Skip to main content
connic

Try every change on staging first.
Production keeps its own keys, data and rules.

Run the same agents in production, staging and dev. Each environment has its own keys, connected systems and data, and its own rules for who may release changes to it.

billing-assistant· same code everywhere
Devconnic dev, local code
StagingSandbox · test customers
ProductionLive · real customers
BILLING_API_URL
billing.example.com/v2
BILLING_API_KEY
••••••••
Mailbox
service@energy.example.com
Deploys by hand
Admin group
Tests run in
Staging

Change it in staging. Customers see it when it's ready.

Take an energy supplier preparing next year's prices. The team tries everything in staging while production keeps answering customers.

The same agent changes monthly installments. Staging uses the billing sandbox with a test key, production the live system.

Billing (sandbox)
billing-sandbox.example.com/installments
BillingSandboxTest key ending 9f2a
Installment changes todayRequested through the API
ChangeCustomerMonthly installmentTimeStatus
IC-30418TC-000184€87 → €9410:42Accepted
IC-30417TC-000112€62 → €5510:39Accepted
IC-30416TC-000301€140 → €41010:31Held

IC-30416 is held for a person: changes of more than 50% need a second look before they reach the customer.

The team loads the 2027 price sheets into staging and checks the answers. One is wrong, so the copy to production waits for the fix.

Answer review
intranet.energy.example.com/reviews/tariffs-2027
Tariff 2027 · answer reviewStagingPrice sheets loaded Nov 3
  • What will I pay per kWh from January?31.84 ct on Home GreenA. Wolf
  • Does my base price change?No, it stays at €11.90 a monthA. Wolf
  • When does my installment change?With the next annual billM. Yilmaz
  • Is there a bonus for switching to Home Green Plus?€50, paid onceShould be €60. Fix the price sheet first.M. Yilmaz

3 of 4 approved. Copy to production once the bonus is fixed.

The same agent answers meter readings sent by email. Staging reads a test mailbox, production the address customers write to.

Service inbox (staging)
service.staging.energy.example.com/inbox
Staging · test mailbox service-test@energy.example.com
My Energy · ServiceInboxCustomersTemplates
  • Meter reading 4821309:12
    TC-000184Answered
  • Moving out on January 3109:05
    TC-000112Answered
  • Why did my installment go up?08:58
    TC-000301For Anna Wolf
Meter reading 48213
Test customer TC-00018409:12

Meter reading 48213 for meter 1EMH 0012 4471, read this morning.

Reply from service-test@energy.example.com09:13

Thank you, we recorded 48,213 kWh for meter 1EMH 0012 4471 on November 3. Your installment of €87 stays the same until your next annual bill.

Production reads and replies through service@energy.example.com.

Production gets stricter rules than staging.

Choose per environment who may release by hand, where its tests run, how long runs are kept and which fields are hidden in logs.

Edit Environment
Production

Deployment and testing

Git Branch
main

Changes to this branch will trigger deployments to this environment.

Test environment
Staging

Where the test framework runs tests/ when deploying to this env.

Deploy Gate Tests

Run tests/ before each deployment ships to this environment.

PR Testing

Run tests here for pull requests targeting main.

Permissions

On-demand deployments
Admin

Selected groups can deploy manually, including through connic deploy. Automatic branch deployments and PR tests are unaffected. Project owners retain access.

Copy from this env
Admin

Choose which groups can copy variables, retrieval data, database collections, and API specs from this environment.

Logs and privacy

Log retention
14d

Use durations such as 1h, 24h, or 5d, with a minimum of 1h.

Sensitive data redaction
*.password, *.secret, *.token, *.api_key, *.access_token, *.refresh_token, *.client_secret, *.private_key

Replace selected JSON field values with [REDACTED] in newly recorded run inputs, outputs, logs, and traces.

Prepare it in staging. Copy it to production.

Copy knowledge, database collections, API specs and variables to production, item by item. Secret values are copied on the server and stay hidden in the browser.

Copy from other env

Copy into Production.

Source environment
Staging
Select namespaces2 selected
  • tariffs-2027
  • price-sheets
  • draft-bonus-offers
Destination environment
Production
If an item already exists
SkipKeep existing items in the destination.
ReplaceUse the data from the source environment.
CancelCopy

One codebase. Each environment brings its own keys and connections.

Tools read variables through os.environ, and the files in connectors/ swap the connection per environment. Each deploy picks up the values of its environment.

connectors/meter-readings.yaml
type: kafka
mode: inbound
name: Meter readings
connection: meter-kafka-staging
config:
  topic: ${METER_READINGS_TOPIC}
agents:
  - billing-assistant
environments:
  Staging: {}
  Production:
    connection: meter-kafka-prod
    config:
      group_id: billing-assistant-prod

Environment VariablesProduction

Variables injected into your agent containers at runtime.

KeyValue
BILLING_API_URLhttps://billing.example.com/v2
BILLING_API_KEY••••••••
METER_READINGS_TOPICmeter-readings
INSTALLMENT_LIMIT_EUR120
tools/billing.py
import os
import httpx

async def change_installment(customer_id: str, amount_eur: float) -> dict:
    """Change a customer's monthly installment in the billing system."""
    async with httpx.AsyncClient(base_url=os.environ["BILLING_API_URL"]) as client:
        response = await client.post(
            f"/customers/{customer_id}/installment",
            headers={"Authorization": f"Bearer {os.environ['BILLING_API_KEY']}"},
            json={"amount_eur": amount_eur},
        )
        response.raise_for_status()
        return response.json()

Frequently Asked Questions

Basic includes one environment, developer three and pro five. Enterprise has no fixed limit. Dev environments created by the dev server don't count toward it.

You pick the permission groups that may release to an environment by hand, and project owners always can. Changes pushed to the Git branch connected to the environment are released regardless.

Keys and other settings, connected systems, database data, Retrieval content, conversations and recorded runs. Log retention and hiding of sensitive fields are set per environment too, so production can keep less than staging.

Yes. A cost limit for one or more environments stops waiting runs there from starting once it is reached, while other environments keep running. An alert with the same scope only sends a notification.