Private-beta doorway published
Atlas SaaS now presents a browser-facing beta surface at the staging hostname instead of leaving evaluators with only an API response and an implicit product story.
Releases
Private-beta release notes explain what hardened, not just what shipped.
Recent contract and boundary changes are visible here so evaluators do not have to infer platform maturity from screenshots, stale assumptions, or operator memory.
Recent milestones
These are the release moves that changed the beta in practical terms.
A useful beta release log tells an invited user or evaluator what got materially better about access, support, trust, and recoverability.
Invite-only registration enforced
Registration now fails closed without a valid invite token, which turns the private beta from a descriptive posture into a real admission boundary.
Support path turned into operator work
Customer support intake now creates a governed manual-only mission so operator follow-up stays inside Mission Control instead of collapsing into informal chat.
Trust contract hydrated
The live release contract now carries real links for docs, status, trust, and preview terms so the customer-facing and trust materials behave like one system.
Release discipline
Each release makes the product boundary clearer and safer.
Private-beta change discipline matters because the product is still earning the right to expand access. Release notes therefore make the control and support boundary clearer over time.
Identity
The current private-beta release identity is `atlas-saas-private-beta-staging`, and the visible ring remains `customer_zero` while the operating model prepares wider invited cohorts.
Contract
Each release preserves the invite-only boundary, hold-first guided mission posture, support-to-operator routing, and explicit rollback authority.
Expectation
Release notes in private beta are meant to explain boundary hardening and operational changes, not to pretend the environment is already GA-stable.
Interpretation
Read these notes as beta hardening, not as a launch announcement.
What changed recently
- Status and preview-terms trust routes were added to the public preview surface.
- Atlas SaaS now publishes final docs, status, trust, and preview-terms URLs in the live release contract.
- Hostname-authenticated support intake has been separately proved over the governing bastion path.
What this still does not mean
- It does not mean GA, public internet launch, or unrestricted external cohort expansion.
- It does not remove the right to freeze, hold, or roll back the environment.
- It does not replace technical diligence, trust inspection, or higher-assurance review where needed.
How this fits
Release notes connect change history back to trust and status.
This page keeps evaluators oriented: what changed, why it matters, and which boundary page to read next.
Before this
Status
Status explains the current operating posture and degradation model.
Open StatusCurrent step
Releases
These recent changes materially hardened the beta boundary.
You are here
Next step
Preview terms
Once the release history is clear, the next move is to inspect the current preview boundary and commitments.
Open Preview terms