Changelog

This page highlights meaningful improvements after they are available to customers.

Entries focus on the product result, affected workflow, and any action customers should take.

Internal infrastructure details, private identifiers, security-sensitive implementation notes, and routine maintenance are intentionally excluded.

Planned work belongs in Availability & Roadmap, not in the changelog.

August 10, 2026

The sidebar now groups guides by customer goal instead of mixing product workflows, internal architecture, and infrastructure ownership.
White-label architecture, customer identity, branding, domains, events, metering, and examples now live together under Build Your Product.
Infrastructure choices, external providers, and provider comparisons now share one Infrastructure section.
Sandboxes, deployment, data, computer, security, and recipe labels use consistent customer-facing language.
Existing documentation URLs remain unchanged, so saved links and integrations continue working.

A clearer path from idea to production

The documentation homepage now leads with the outcomes teams can achieve instead of presenting Sandboxes as the primary product promise.
A three-stage journey explains how agents create software safely, prove the result, and deploy one verified release.
Goal-based starting paths connect application development, Agent Runs, computer automation, and customer-controlled infrastructure to the relevant guides.
Production release proof remains visible without requiring new users to understand every command before they begin.
The refreshed homepage supports keyboard navigation, reduced motion, mobile layouts, and accessible contrast in light and dark themes.

Operational documentation and safer discovery

Projects now have a dedicated conceptual guide that separates ownership from Sandboxes, Computers, and Deployments.
Domain guidance now translates DNS-provider fields and shows the complete ownership, certificate, and routing sequence.
Recovery playbooks provide symptom-first checks for deployments, domains, TLS, App Engine hosts, and Sandbox previews.
Documentation search recognizes common customer language while returning canonical MIOSA concepts.
Public changelog checks reject common private identifiers before publication.
Documentation feedback sends only the page path, rating, and feedback source, with no query string or customer-entered content.

No customer action is required.

Documentation search

Search now ranks direct title and phrase matches ahead of weaker body and terminology matches.
Results can open a matching section directly instead of stopping at the top of its page.
Common product aliases remain discoverable without diluting exact matches.
The selected result now uses one quiet neutral surface with a clear destination arrow instead of a stacked accent treatment.
Search supports mouse, keyboard, screen-reader, light-theme, dark-theme, and mobile navigation.

Guided learning paths and clearer terminology

The documentation now provides a guided education layer across the existing technical references, cookbook workflows, and API guides.

Learning paths

A new Learning Paths hub organizes existing documentation around four outcomes: deploying a first production app, building an agent product, automating a desktop, and building a white-label platform.
Every path defines an ordered reading sequence, expected result, proof requirement, recovery expectation, and finish line.
A compute chooser explains when to begin with a Sandbox, Computer, App Engine Host, Bring Your Own Cloud region, or OpenComputer.

Complete Next.js example

A new Next.js tutorial takes an application from an empty Sandbox through Preview, App Engine publishing, Deployment proof, custom-domain verification, safe updates, and rollback.
Expected results appear after each major step instead of leaving readers to infer whether an operation succeeded.
A symptom-first recovery table covers pending capacity, broken previews, unavailable App Engine Hosts, incomplete promotion, DNS verification, incorrect domain ownership, and application regressions.
The tutorial ends with an explicit completion checklist and production-hardening links for databases, secrets, publishing, and domains.

MIOSA glossary

A visual flow shows how work moves from Organization and Workspace through Sandbox, Release, Version, Deployment, and Domain.
“Do not confuse” guidance separates User and Organization, Release and Version, Deployment and Runtime Instance, and Bring Your Own Cloud and OpenComputers.
Definitions cover customer-visible ownership, development, deployment, domain, agent, data, security, infrastructure, and billing concepts.
Private infrastructure details and security-sensitive implementation notes remain excluded.

The selected page now uses a quiet neutral surface and subtle border instead of a colored gradient and glow.
Parent groups stay visually calm while the exact current page remains clear.
Hover and keyboard-focus states remain distinct in both light and dark themes.

August 9, 2026

A clearer documentation experience

The documentation now uses one navigation system and a more focused reading layout.

Search, appearance controls, page navigation, and Ask OSA are easier to find.
Ask OSA opens beside the article without replacing or shrinking the documentation landing experience.
The assistant panel can be resized to fit different screens and reading preferences.
Generated search and AI indexes were refreshed to match the public documentation.

Domain setup and deployment URLs

Domain configuration now explains the difference between platform-provided deployment URLs and customer-owned domains more clearly.

Organization domain setup presents the required DNS record and verification state in one flow.
Deployment screens show which hostname is currently serving the application.
Custom deployment domains remain scoped to the owning organization and deployment.
DNS, certificate, and routing states use clearer status language and recovery guidance.

Onboarding improvements

New organizations can configure team access and domain setup during onboarding.

The final onboarding step now provides clearer next actions for using the platform, CLI, and agent workflows.

August 5 - 8, 2026

Faster, more dependable computers

Computer creation and reconnection were improved across gallery, workspace, and embedded desktop experiences.

Warm computers can open with less waiting when compatible capacity is available.
Desktop sessions recover more reliably after navigation, refreshes, and temporary connection loss.
Gallery cards distinguish usable live desktops from failed or incomplete previews.
Lifecycle buttons reflect the operation the platform can actually perform.
Creation limits and available capacity are shown before customers submit incompatible requests.
Viewer access controls are available from the computer workspace.

See Computers for the current workflow.

Account and organization access

Account security and team administration received a substantial usability update.

Email verification is required for new signups.
Personal organizations remain available when a user later creates or joins a company organization.
Member roles, invitations, pending access, and organization context are easier to understand.
Account security controls are available from the live settings experience.
Mobile administration navigation was improved.

API key and CLI guidance

Setup screens now separate browser login, API keys, and CLI authentication more clearly.

Examples point customers toward the appropriate credential for each environment instead of presenting unrelated authentication methods as interchangeable.

July 29 - August 1, 2026

App Engine and deployment workflows

App Engine now has a dedicated product surface for managing application deployments.

Application domains, preview URLs, and management links are presented as separate concepts.
Direct-upload previews are available for supported deployment workflows.
Deployment views expose current state and recovery information more consistently.
Public status is based on the running application and route, not only saved metadata.

See Deployments for the current publishing and promotion model.

Sandboxes and operational access

Sandbox management gained clearer runtime controls and operational access.

Terminal and SSH access are available for supported sandboxes.
Runtime actions are organized around the selected workspace and sandbox.
The operations view makes current state and available actions easier to scan.

Data and integrations

Database, storage, network, and integration screens now expose more of the state customers need to operate them safely.

Database pages show lifecycle, health, recovery, and capacity information.
Storage creation respects plan capacity before submission.
Integration access is visible across the platform areas that can use it.
Integration setup and marketplace navigation are more consistent across desktop and mobile layouts.
Customer-cloud placement remains gated by provider verification and workload capability.

Workspace-scoped assistance

Optimal conversations, tasks, approvals, investigations, and artifacts now remain attached to the selected workspace and resource context.

This makes it easier to return to prior work without mixing unrelated organization or project history.

July 24, 2026

Public contracts and deployment guidance

The CLI, API, SDK, data, domain, release, and deployment guides were aligned with the shipped platform contracts.

API examples use the current production base URL and credential families.
Sandbox snapshots, restore, fork, and lifecycle operations are documented.
Release creation, exact promotion, production proof, and rollback are documented as separate steps.
Managed database lifecycle, credentials, backups, restores, logs, metrics, and placement are covered.
Documentation checks reject known stale commands, paths, and hostname patterns.

Usage and platform controls

Usage and billing surfaces now use consistent USD and credit meanings.

The Action Authority experience supports constrained approvals for sensitive operations.

July 7 - 19, 2026

Production workflows

App Engine became the customer-facing workspace container runtime.
Deployment proof was added to the product and documentation.
Sandbox capacity, persistence, readiness, and resource sizes became catalog-driven.
Organization switching, invitation recovery, and domain settings were clarified.
Agent Runs added durable execution, cancellation, artifacts, runtime profiles, and grouped workflows.
Data documentation expanded across authentication, storage, volumes, and managed services.

May - June 2026

Platform foundation

MIOSA introduced the first production versions of its unified workspace, sandbox, computer, deployment, data, billing, and agent workflows.

Major additions included:

Durable onboarding and organization context.
Isolated sandbox execution, files, previews, snapshots, and forks.
Persistent computers and embeddable desktop sessions.
Managed application deployments and custom domains.
Usage metering, prepaid credits, and plan controls.
White-label attribution, branding, scoped tokens, and webhooks.
SDKs, CLI tooling, MCP support, and framework integrations.

See the current product documentation for supported behavior and Availability & Roadmap for maturity boundaries.