Releases and versioning

Availability

Alpha — unsigned Windows build. Actorvia is an early alpha: an unsigned Windows application and a Roblox Studio plugin. Subscribe and both are downloadable immediately, but connecting a project to Studio is a manual pairing step rather than a one-click setup.

Create an account to subscribe. The runtime package and the Studio plugin are issued to your account as soon as the subscription is active.

What the plans include

The runtime is sold in three tiers — Starter at $20 per month, Builder at $50 per month, Studio at $100 per month, each also available annually. Every tier includes the same complete runtime; what scales between them is commercial, not technical:

• Starter — 1 active project, 1 developer seat.
• Builder — 5 active projects, 2 developer seats.
• Studio — 20 active projects, 5 developer seats.

Accounts on the original Pro (legacy) plan keep it unchanged; it maps to Studio-equivalent scale. Every tier covers:

• The complete core runtime — no plan gets a smaller brain
• Full SDK, Studio workflow and plugin
• Domain-pack authoring and validation tooling
• Scenario testing and diagnostics tooling
• Every release as it ships, including major versions
• Execution happens inside your own Roblox servers

Versioning

Releases are versioned MAJOR.MINOR.PATCH. A patch release fixes behaviour without changing an interface. A minor release adds capability that existing packs and adapters keep working across. A major release is the only kind that may change an interface you already depend on.

Every release ships with notes. A major release additionally ships a migration note that names each changed interface and what to do about it.

Breaking changes

The commitment is procedural, and it holds in both directions:

• Interface changes land in a major release, never in a patch.
• Every breaking change is published in release notes with a migration note.
• Pack validation reports which roles a change affects before you ship it.
• The previous major line keeps receiving security fixes for six months.

What is not promised

• No contractual uptime guarantee — the runtime executes inside your own Roblox servers
• No support channel during the alpha — there is no support inbox and no named engineer
• No custom domain-pack development or bespoke integration work
• No third-party security audit has been published.

Pricing is published in full on the pricing page, including exactly what the plans do not commit to.