Config · secrets · feature flags

A config change broke checkout at 2pm. Ask who changed it, and what it broke.

Config, secrets, and feature flags in one typed schema, for every environment and every language you run. Every change is checked before it lands and recorded after, so Smooth Operator can tell you exactly what happened.

Set up your first schemaWalk through your setup with us
  • TypeScript · Python · Rust · Go
  • Checked against your schema
  • Every change on the record

Ask what changed. Make the fix yourself.

Smooth Operator reads the audit trail and the new errors, tells you who flipped what, and leaves the change to you.

◍ Smooth Operator
Set up your first schemaWalk through your setup with us

One schema, every environment. Each one kept apart.

The Configuration page: development, production, and staging environments, with tabs for schemas, values, feature flags, and limits.
The Configuration page. Development, staging, and production, each with its own values, flags, and secrets.
Two developers working side by side at a bright desk, a laptop on a stand between them

Three kinds of key

Public
Safe to ship to the browser: API URLs, display settings
Secret
Server only, encrypted at rest: API keys, tokens, passwords
Feature flag
On or off per environment, so staging can run ahead of production
  • $ pnpm add @smooai/config
  • $ pip install smooai-config
  • $ cargo add smooai-config
  • $ go get github.com/SmooAI/config/go/config

It owns the execution. You own the constraints.

The schema says no first.

Every value is checked against the schema you wrote. A string where a URL belongs never makes it into an environment.

Secrets stay secret.

Secret values are encrypted with AES-256-GCM under a key that belongs to your organization alone, and that key rotates every day.

Every change is on the record.

Setting a value or flipping a flag writes an audit event: who, which key, which environment, when.

Only admins can write.

Everyone in your organization can read config. Changing it takes an admin.

Smooth Operator can’t change it at all.

It can tell you who changed what and what broke after. The change itself stays with you.

  • A bad value never lands.
  • Every change is on the record.
  • Nothing changes without a person.

Fair questions

The questions people ask first. Straight answers.

Will this replace my team?

No. Your engineers still decide what goes in config and when it changes. What goes away is the hour spent working out which change broke what, because the record already knows and Smooth Operator can read it to you.

Which languages does it support?

TypeScript, Python, Rust, and Go, all reading the same schema. You define it once, with types, and every service gets autocomplete and a clear error instead of a silent undefined.

Can Smooth Operator change a config value?

No. It has no tool that writes config. It reads the audit trail and the error groups so you know what happened, then you make the change on the Config page or with smoo config.

How are secrets protected?

Secret values are encrypted with AES-256-GCM under a per-organization key, and the key rotates daily. Only admins can write, and every write is audited.

What does it cost?

Config is $19/mo on top of any AI plan, or part of the Platform Bundle.

How is this different from a .env file or a secrets vault?

A .env file has no types and no history. A vault keeps secrets but not the flags and settings next to them. Here they live together, typed, with a record Smooth Operator can read when something breaks. ChatGPT helps you think. Smooth Operator does the work, inside your business.

Next time a change breaks something, know who and what in one question.

Config is $19/mo on top of any AI plan. Define one schema and every service reads it.

Set up your first schemaWalk through your setup with us