Private development Local Zora stays offlineEnvironment & release path
← Meet Zora Open private staging ↗

A place to build
the living company.

This is the private development environment for Zora Constellation. Explore the glass experience, account controls, guided story, and investor model here while the company systems are completed and verified.

Separate by design

A separate site and database. Development accounts and conversations stay here.

Your Zora stays offline

The canonical gateway is disabled in this build, even if gateway secrets are accidentally supplied. No local Zora process is started.

Truthful capabilities

The guided tour is authored. Open-ended AI requires a separately configured cloud service. Consent can route a visitor-approved summary into an identity-free company review queue; assessment is not yet connected. Live payments and live trading are unavailable.

Separate development and staging

Open the private staging environment ↗. It uses a separate project and database and keeps local Zora, payments and live trading disabled.

Development → validation → production

  1. Build and test in this private environment with synthetic information and separate service credentials.
  2. Verify the complete Meet Zora journey, account privacy, company approvals, cost limits, and ZoraTrade paper-mode workflow against recorded acceptance criteria.
  3. Prepare a release candidate with its source revision, migration checksums, test results, dependencies, rollback instructions, and unresolved gates.
  4. Review the candidate before promoting the same application source into production. Configure production identity and providers separately; do not copy development users, conversations, or secrets.
  5. Run production smoke checks and observe the release. Restore the previous application version if needed; review database recovery separately.

Execution documents

Open the human and machine execution library. Local reference-runtime tests are development evidence; they do not certify cloud operation or production readiness.

The Cloudflare infrastructure here is managed by Sites. Moving into a company-owned Cloudflare account requires that account’s authorized deployment access and an identity integration review.