Skip to main content
Help Center

Prepare a Sandbox Environment in Batoi Build

Register a bounded non-production target and verify its app context, public entry point, health route, and rollback boundary.

3 min readVerified Aug 17, 2026Batoi Platform
Guide navigation 6 of 42
Browse all 42 articles
Business view

What this page helps you accomplish

Register a bounded non-production target and verify its app context, public entry point, health route, and rollback boundary.

Batoi Platform · Build
Accountable roleWorkspace Admin, Builder, Release Owner
Business taskDeployment
Completion signalA bounded sandbox target is app-scoped, reachable, independently verifiable, and clearly separate from beta and live.
1 Confirm

Scope and authority

A Batoi Build App with its approved canonical source mode verified Authority for the intended non-production hosting target and credential boundary

2 Act

Deployment

Register a bounded non-production target and verify its app context, public entry point, health route, and rollback boundary.

3 Verify

Observable business result

A bounded sandbox target is app-scoped, reachable, independently verifiable, and clearly separate from beta and live.

Potential issue and recovery

The expected record or action is missing.

Recommended recovery: Return to the intended context and ask an Owner or Admin to confirm access. Do not use another person’s account.

Who should use this article

This article is for Workspace Admins, Builders, and Release Owners who are authorized to complete or review this task. A consequential decision remains with the accountable person.

Before you begin

  • A Batoi Build App with its approved canonical source mode verified
  • Authority for the intended non-production hosting target and credential boundary
  • An assigned deployment and rollback owner
  • Use approved sample or operational information only. Never enter a password, token, private key, or unnecessary personal information.

Open Hosting Targets

  1. Open the selected app in Build.
  2. Expand Settings and choose Hosting Targets.
  3. Select an existing app-scoped target or add the approved development target.
Sandbox preparation workflow A reviewed source revision or artifact is published to a bounded development target, followed by homepage, health, data adapter, and rollback checks. Prepare a target that can be verified safely Reviewed Source Canonical source revision or artifact Sandbox Target DEV domain, credential boundary, rollback owner Independent Verification Homepage, health, data, security, and rollback
Sandbox readiness includes both target configuration and independent runtime checks.

Configure the target

  1. Use an environment-specific name and select the development or sandbox tier.
  2. Associate the exact App, approved canonical source, and intended domain.
  3. Keep hosting credentials in the approved secure store. Record only the safe reference needed by Build.
  4. Assign deployment and rollback responsibility.
  5. Use Ready only after the target can be reached and its app context is correct.
Batoi Build Hosting Targets
Reference screen: the register should state that only the selected app's target records are shown.

Verify the sandbox

  • The homepage loads over HTTPS.
  • The health route returns a successful response.
  • The selected source revision is identifiable.
  • The app-scoped database adapter works without revealing credentials.
  • Required Guard checks and rollback conditions are defined before promotion.
Batoi Build Hosting Targets
Reference screen: a minimal baseline homepage makes the deployed app identity and health route visible.

Continue with Connect an Application Database in Batoi Build.

Troubleshooting and recovery

What you seeWhat to checkSafe next action
The expected record or action is missing.Workspace, project/app context, role, status filters, and prerequisites.Return to the intended context and ask an Owner or Admin to confirm access. Do not use another person’s account.
The status remains incomplete or needs review.Required fields, evidence, approvals, source connections, checks, and owners.Record the missing item and owner. Do not mark the task complete until it can be independently verified.
The result conflicts with policy or evidence.Scope, source recency, exception authority, decision conditions, and reviewer independence.Do not bypass the control. Return the item for correction or escalate it through the authorized route.

Safety and governance

Protect sensitive information. Do not place credentials, secrets, private keys, raw tokens, unnecessary personal information, private repository content, customer identifiers, or restricted documents in a public note, screenshot, prompt, export, or evidence caption. Use approved secret references and permission-controlled workspace records.

Final verification

Expected result: A bounded sandbox target is app-scoped, reachable, independently verifiable, and clearly separate from beta and live.

Next step

Continue with the next verified article in this Product Guide, or return to the Batoi Platform Product Guide.