Availability & Roadmap

This page gives customers a clean read on what is ready for production today, what is available for selected partners, and what is still on the roadmap.

Release stages

Stage	Meaning
Generally available	Supported for production use with documented APIs and normal support paths.
Partner preview	Available to approved customers while we finish polish, SDK parity, or operating runbooks.
In hardening	Built or partially available, but not ready to promise as a stable public surface.
Planned	On the roadmap, not available for production use yet.

Generally available

Create isolated Linux workspaces for code generation, build steps, test runs, long-running commands, file operations, and live previews.

Expose a running process on a public preview URL, with private preview tokens for embedded product experiences.

Turn a sandbox into a durable deployment version, promote it, list versions, and roll back when needed.

Use external IDs, browser tokens, custom branding, preview domains, webhooks, and usage rollups to build MIOSA into your own product.

Partner preview

These surfaces are being used with selected customers while we continue polishing public docs and SDK parity.

Surface	Current scope
Computers	Full Linux desktops for browser automation, screenshot loops, and computer-use agents.
Dynamic deployments	Production server processes created from a sandbox publish.
Tenant deployment domains	Branded app domains for generated apps, separate from sandbox preview domains.
External computer providers	Bring third-party computer providers into the same MIOSA computer abstraction.
Evaluations	Desktop and agent workflow benchmarks using reproducible tasks, traces, and scoring.

In hardening

Area	Status
Desktop computer provisioning	Desktop images, resume behavior, and stream readiness are being hardened for faster and more predictable starts.
Dynamic runtime routing	Dynamic runtimes support public serving, health checks, and replacement. We continue tightening route reporting across CLI and API surfaces.
Managed data services	Postgres, Redis, object storage, auth, and volumes are documented as target surfaces. Production rollout is staged by customer need.
SDK parity	Python is the deepest SDK today. TypeScript, Go, Java, and Elixir are being brought to the same coverage over time.
Cross-workspace analytics	Resource attribution is live. Higher-level dashboards and billing views are expanding.

Planned

Capability	Notes
Native GPU sandboxes	Planned for workloads that need accelerated inference or rendering.
Edge functions	Planned as a deployment target separate from origin runtimes.
Native nameservers	Planned for customers who want MIOSA to manage more of the domain lifecycle.
OTLP export	Planned for teams that want platform traces in their own observability stack.
Test-mode API keys	Planned to separate production billing from integration testing.

MIOSA is not trying to be a generic Kubernetes replacement, commodity VPS provider, or blockchain platform. The product is focused on AI-generated software, isolated execution, live previews, desktop automation, white-label SaaS infrastructure, and durable deployment.