Beta

Early Beta Access is the free plan every workspace starts on. The allowances, what is included, how limits behave, what changes at 1.0, and how paid plans arrive.

Anlyon is in early beta. The API contract can change before 1.0, and every change is announced in the changelog with a migration note.

The current terms are always the ones the API reports: GET /api/v2/public/pricing-policy (unauthenticated), the pricing page, and Settings → Plan & Billing in the console. They are read from the API’s release setting, so they match what the API enforces. This page explains Early Beta Access, the terms in force while mode is early_beta.

Early Beta Access

Early Beta Access is the free plan every workspace starts on.

• Self-serve signup. No invitation required.
• Free within hard limits. The allowances are listed below and enforced by the API. The console and pricing page show the same numbers.
• No card, no subscription, no overage. Nothing is charged automatically. Paid plans arrive after the beta.
• Changes are announced before they take effect. We review the offer after 30 days. If an allowance changes we tell you before it takes effect. There is no account-expiry countdown.
• Paying is always opt-in. When paid plans open, moving to one is your explicit choice. Nobody is converted, charged, reset, or deleted by that change.

Allowances

Monthly allowances (executions, messages, egress, email alerts, Vigil reviews) reset at 00:00 UTC on the first of each month. Stored data, seats, environments, and action definitions are limits on what you hold, so they do not reset. Other rate, retry, payload, and resource limits are unchanged from the standard Free plan.

What is included

• Three environments of any kind. A new workspace starts with one protected environment of kind production, named Production. You can add staging and development kinds and change an environment’s kind in the console or through the API. See Environments.
• Environment protection and controlled promotion between environments.
• The email notification channel, up to 500 emails per workspace per UTC month.
• Halt, isolation, approvals and approval policies, immutable versions and rollback.
• Traces, spans and approval decisions, with no separate charge.

When you reach a limit

Requests stop at a hard limit, with a machine-readable QUOTA_EXCEEDED error. Nothing is charged. What to do:

There is no guaranteed response time and no guaranteed limit increase. Inspecting and deleting your own data always works, even at a limit.

Stability

openapi.yaml is the contract. The API reference is generated from it, and CI checks the backend routes and both SDKs against it, so “the SDK does something the API reference doesn’t” is a bug, not a grey area.

What the contract covers today:

• The v2 REST API and both SDKs (@anlyonhq/sdk, anlyon).
• Environments and the kill switch, approvals and approval policies, immutable versions and rollback, budgets.
• The earlier namespaces: messages, schedules, URL groups, workflows, events, queues, the dead letter queue, memory, sessions, context assembly, files and semantic cache. They are kept as they are, and no new capability is planned for them.
• Runs and traces, including OpenTelemetry export.

Most likely to change before 1.0:

• Response-shape details on the analytics endpoints.
• Newer SDK ergonomics helpers layered on top of the core client.

Changes to the API

The API contract can change before 1.0. Every change is listed in the changelog with a migration note. That covers a removed or renamed field, a narrower type, a new required parameter, a changed default and a changed status code.

New endpoints, new optional fields and new enum values are added as the product grows. Write your integrations to ignore fields they do not recognise.

Availability

Anlyon publishes a status page and has no uptime SLA yet.

• The status page shows live and historical availability.
• Incident notes for user-visible outages are posted to the status page.
• Three controls are worth stating precisely. Halting an environment stops new dispatch out of it. A request an external server has already accepted is not recalled. A capped key is refused further Anlyon operations. That is a cap on those operations and not on model tokens or on money an approved action moves. Rollback repoints an agent at an earlier immutable version. It restores the definitions later calls run and does not undo an effect already dispatched.

Support

• Email support@anlyon.com. We read everything. There is no guaranteed response time.
• GitHub. The source repositories are private. Public discussions are at github.com/AnlyonHQ/community.

Tell us what’s rough. Feedback sent now changes the roadmap. Send feedback and Contact support are also in Settings → Plan & Billing.

How paid plans arrive

Paid plans arrive after the beta. Production is planned at about $49 a month and Growth at about $199 a month, and Enterprise is by contract. The prices on the pricing page are planned and may change before paid plans open. Reference documentation for them is in Billing & Pricing.

When paid plans open:

• Your workspace stays on Free. Nothing converts you to a paid plan.
• Existing Early Beta workspaces keep their beta allowances for a transition window that is announced in advance. Its end date is fixed once set and does not restart.
• Above the standard Free limits, creating new resources may be blocked after that window, while inspecting, exporting, and deleting stay available.
• Your data and usage are never reset or deleted by the change.

What changes at 1.0

Anlyon reaches 1.0 when these three things are in place:

• There is a meaningful stretch of availability history on the status page.
• A written SLA with service credits is published.
• Support has response-time targets.

At 1.0 the sentence at the top of this page is removed. There is no date for 1.0.