Plans, Limits & Trial

Overview

Veltrix has four plans: Free, Starter, Professional and Enterprise. A plan sets two things: limits (how many users, apps, canvases and so on you can have) and capabilities (whether features such as drift detection, approval workflows or MCP access are available). Limits and capabilities are enforced by the server, so they hold for the portal, the CLI, API keys and AI assistants alike.

This page describes plans by feature and limit. For prices, see the Pricing page. Whether you can purchase a plan or add a card in a given workspace depends on billing being enabled for that deployment; when it is not, the Billing page says “Billing isn't configured yet”.

Where to Find It

• Portal: Govern → Settings → Billing, route /settings/billing.
• Permissions: subscription:read to see the plan and usage, subscription:write to start checkout, open the billing portal or extend a trial, and payment:read / payment:write to view and change payment methods. Administrators hold all of these.

Plan Capabilities

Local email and password sign-in, API keys and the Organization settings are available on every plan. Enterprise is not self-serve: the Billing page shows a Contact sales card for it instead of a checkout button.

Plan Limits

These are the plan defaults. A platform operator, or an MSSP managing your organization within its own caps, can set per-organization overrides for users, apps, components and canvases, so your effective limit can differ from the table. The Billing page always shows your effective numbers.

What happens at a limit

• Quota limits (users, enabled apps, canvases, components, concurrent deployments) return HTTP 429 with a message such as “Canvas limit reached (1 for free tier)”. Existing resources are not touched. Quota checks reserve a slot atomically, so two simultaneous requests cannot both slip past the limit.
• Capability gates return HTTP 403 with an upgrade message, for example “Approval workflows require a paid plan” or “MCP access requires a paid plan”.
• The portal hides or replaces gated screens with an upgrade prompt where it can, for example the Role Management and Identity Provider tabs on the free plan.

The Billing Page

The page is made of these panels, top to bottom:

Change plan

1. In Upgrade / Change Plan, choose the plan card. The button reads “Start 14-day free trial” if you are still trial-eligible, otherwise “Upgrade”.
2. You are redirected to the payment provider's hosted checkout. On return, the page confirms “Your subscription was updated successfully!” or “Checkout was canceled. Your plan was not changed.”
3. To change the card, cancel, or reactivate a plan set to cancel, use Manage billing, which opens the provider's billing portal. A plan set to cancel shows a “Subscription ending” notice: you keep access until the period end.

Add a payment method

1. Select Add Payment Method.
2. Enter the Name on Card and the card details in the secure card field. Card data goes to the payment provider, not to Veltrix.
3. Submit. On success the card appears in the list; use Set Default to choose which card is charged.

The 14-Day Trial

1. Start. From Billing → Upgrade / Change Plan, a trial-eligible organization (one that has never started a paid subscription) picks Starter or Professional and starts a 14-day free trial. You get that plan's limits and capabilities for the duration. A card is not required to start.
2. During the trial. The Billing page shows “Trial active — N days left” and reminds you to add a payment method before it ends.
3. After day 14 without a card. The trial ends. If you do not add a card, the subscription is cancelled rather than silently charged.
4. Hard block. An organization that started a trial, whose trial or subscription has lapsed and that has no chargeable card, is blocked from meaningful work: requests that change things (create, update, delete, deploy) return HTTP 402 “Your trial has ended. Add a payment method or request an extension to continue.” Reading data, and reaching the Billing page to fix the problem, stays available.
5. One extension. The trial banner offers Extend 14 days once. It is available while a trial is active, or if the trial just lapsed and you have never paid an invoice. It is not available on an active or past-due subscription (use Manage billing instead). After the one self-serve extension is used, adding a card is the way forward. Veltrix operators can grant further extensions.
6. Add a card (or use Manage billing) and write access is restored.

The hard block covers every route group that changes tenant data — canvases, pipeline and deployments, apps, components, credentials, environments, connectivity, ticketing and API keys — so an automation using an API key sees the same 402 as a person in the portal.

Downgrades and Over-Limit Organizations

Limits are checked when something is created. If your plan goes down (a downgrade or cancellation), you keep everything you already have, all still readable, but you may now be over the new limits. In that state:

• Creating more of the over-limit resource is refused (429).
• Editing an existing over-limit canvas or component is refused (403) with a message telling you how many to remove, or to upgrade. Deleting the excess, and reading, still work.

Remove the excess or move back up a plan to resume editing.

Audit and Log Retention

The retention window in the capability table applies to log entries, audit events, configuration history and deployment logs. A daily job removes records older than your plan's window. Paid plans are purged on that schedule. For the Free plan, purging is switched on by the platform operators after notice, so free-plan history may be retained longer than 7 days until then — plan your exports on the 7-day figure.

Past-Due and Hosted Infrastructure

Veltrix-hosted bring-your-own-license infrastructure is metered and billed to your account. New provisioning requires a chargeable card and an active plan. If an organization stays past due beyond a grace period (7 days by default, shorter for cancelled or suspended subscriptions), Veltrix may decommission its Veltrix-hosted infrastructure so it does not keep incurring cloud cost. Infrastructure running in your own cloud accounts is not affected by this.

Gotchas

• The trial runs on the plan you picked at checkout, not automatically on the highest plan.
• Enterprise is arranged with sales; it has no self-serve checkout.
• Users, apps and canvases count everything in the organization, including those created by API keys and AI assistants.
• Plan and payment changes need subscription:write and payment:write; the role editor offers both (and payment:read / subscription:read), so billing can be delegated to a custom role without granting full Administrator access.
• Prices on the Billing page come from the payment provider's configuration, so they are not repeated in this documentation.