Environments & Isolation

An Environment is an isolated deployment stage within a Project. Naagmani provides native two-tier environment isolation: Test and Production.

graph LR
    subgraph Test["Test Environment (Sandbox)"]
        TestToken["nst_live_... (Test Env)"] --> TestModel["gpt-4o-mini / Synthetic Data"]
    end
    subgraph Prod["Production Environment"]
        ProdToken["nst_live_... (Prod Env)"] --> ProdModel["gpt-4o + Fallback Cascade"]
    end

Two-Tier Environment Architecture #

Naagmani consolidates workloads into two distinct, cryptographically isolated tiers:

Environment Isolation Guarantees #

1. Secret & Key Isolation: Service tokens and credentials issued for the test environment are strictly rejected in production.
2. Dedicated Routing Rules: Use inexpensive, fast models in Test while enforcing strict high-availability fallback cascades and circuit breakers in Production.
3. Telemetry & Quota Tagging: Usage analytics, provider attempts, and audit logs are partitioned by environment, enabling clear cost segregation between testing and live operations.

Managing Environments in the Developer Portal #

• In the Developer Portal, the active environment is selectable from the top navigation and project sidebar.
• When generating Project Service Tokens or API Keys, you must explicitly bind the token to its target environment (Test or Production).

Next Steps #

• Learn about API keys: API Keys & Vault
• Learn about service tokens: Project Service Tokens