Skip to main content

Environments & Deployment

Boltic Gateway provides a robust dual-environment setup to support safe, iterative development and controlled production rollouts. This separation ensures that developers can test changes quickly without impacting live traffic, while production deployments remain stable and deliberate.

Test Environment​

  • Auto-Deploy on Save: Any updates to routes, integrations, or gateway configurations are instantly deployed upon saving.

  • Rapid Feedback Loop: Ideal for iterative testing and development, changes reflect almost immediately—typically within a few seconds.

  • Unique Subdomain: Each gateway is assigned a dedicated test domain (e.g., {your-gateway-id}.boltic.app), isolated from production traffic.

  • No Approval Required: Useful for experimenting with new workflows, headers, rewrites, or middleware logic without needing a manual trigger.

    Test Domain
tip

Changes to the test environment are automatically deployed upon saving, providing a rapid feedback loop for developers.

Production Environment​

  • Manual Deployment Required: All changes must be explicitly deployed via the UI or API to reach the production environment—ensuring high confidence and control.

  • Stable & Controlled: Guarantees that only validated configurations go live, minimizing the risk of regressions or errors in critical traffic paths.

  • Dedicated Production Domain: Each gateway has its own production subdomain (e.g., {your-gateway-slug}.boltic.app), separate from the test domain.

  • Rollback Support: Roll back instantly to any previously deployed production version in case of issues.

    Prod Domain
warning

Changes in the production environment require manual deployment, ensuring a controlled and deliberate approach to traffic management.

Deployment Behavior​

  • Propagation Time: Changes in either environment typically reflect within 5–10 seconds post-deployment.

  • Deployment History & Audit Trail:

    • View all prior changes, timestamps, and the user who performed the action.

      View Change History

    • Roll back to earlier configurations with a single click—helpful in case of breaking changes or unexpected behavior.

      View deployments
      Revert to specific version

Best Practices​

  • Use the test environment to validate changes before every production rollout.
  • Keep an eye on the deployment history for audit and debugging.
  • Leverage rollback when a deployment causes unexpected behavior in production.