Docs / Getting started

In the beta

What the beta gives you, which numbers apply, where your calls may go, what is not available, and what leaves when you leave.

What the beta gives you

• A tenant of your own, sealed off from every other tenant on the installation.
• Two environments, sandbox and production, with promotion between them.
• The role of tenant admin: you invite colleagues, open write probes for the sandbox, allow egress ranges, and clear health marks. What each role may do is on People and access.
• Access in the browser, from the command line and over MCP, with tokens bound to one environment that expire within 14 days.
• The beta runs for eight weeks from your invitation. Its data sits on one server in Germany.

Limits are the defaults

Every ceiling in the beta is the installation’s default. The platform’s own table is Limits and safety; the ones you meet first are on Start here.

Where your calls may go

An outbound call reaches any public address. Private address space is denied unless you, as tenant admin, allow ranges for an environment — and in the beta the installation’s own network is not yours, so a system reachable only inside your network cannot be called. Cloud metadata addresses are refused always, whatever the list says.

Apps {#apps}

The beta has no apps host: an endpoint set to app cannot serve a folder of files at an address of its own here, and the app users’ completion page is not available. The other three interpretations — webhook, API, MCP — work as documented.

Not available

These are absent in the beta. None of them is promised.

• A chat assistant inside the product.
• Importing an API description (OpenAPI) into functions.
• An on-premises agent that reaches into your network.
• Single sign-on for the authoring interface.
• SQL and GraphQL as function types (a GraphQL API is called through an http function whose POST body carries the query).
• Gmail as a mailbox.
• More than one machine behind a tenant.
• A custom domain for your endpoints.
• Encryption of the whole database at rest (registered secrets are encrypted; scripts, configuration, run records and datasets are stored in plain form on the volume).
• Pricing, a service-level agreement, support hours.

What leaves when you leave

Deleting your tenant removes configuration, history, credentials, runs, files and staged data, and is reported finished only when every machine of the installation has confirmed. What stays: the record of who changed what (the authoring trail is never pruned by age), the record of what ran for 365 days, and a backup taken before the deletion, which restores the tenant whole and is aged out after 30 days.