Skip to content
Apex
Aether Cloud / Developer tools / Feature flags
Aether Cloud · Developer tools

Feature flags.

Progressive delivery, targeting and experiments with instant rollback.

⌨ Developer tools
Overview

Decouple deploy from release — roll features out by cohort, run experiments and kill a bad change instantly, without a redeploy, across apps, models and prompts.

Where it sits
Deployment
Managed → air-gapped
Governance
IAM · encryption · audit
How it works

Three steps to running.

01
Wrap a feature

Decouple deploy from release behind a flag.

02
Target

Roll out by user, cohort, region or percentage.

03
Experiment & kill

A/B test, or disable instantly without a deploy.

What you get

Feature flags, in full.

Targeted rollout

Release by user, cohort, region or percentage.

Experiments

A/B and multivariate tests with built-in stats.

Kill switch

Disable a feature instantly without a deploy.

Model & prompt flags

Flag model versions and prompts, not just code.

API-first

Provision it in a few lines.

Every service is reachable from the same SDK, CLI and infrastructure-as-code — one identity, one bill, one audit trail across the whole catalog.

# Provision feature flags on Aether Cloud
aether developer-tools create \
  --service feature-flags \
  --name app \
  --region us-1 \
  --deploy managed   # or vpc | on-prem | air-gapped
Specs

At a glance.

Targeting
User · cohort · region · %
Experiments
A/B + multivariate
Kill switch
Instant, no deploy
Scope
Code · models · prompts
Stats
Built-in significance
Use cases

Built for real work.

01

Progressive delivery

02

A/B experimentation

03

Safe model rollouts

Why one platform

On one model, not stitched together.

The usual stack runs feature flags in one product, the model in another and the data in a third — and the seams between them are the cost. Aether Cloud runs it on the same platform that serves the model, governs your identity and deploys into your boundary, with the rest of the catalog one hop away.

One platform

No stitching a vector DB to one place, a warehouse to another and a model to a third — feature flags sits next to the rest of the catalog, one identity, one bill.

The model is here

The provider that runs Aether runs your feature flags — so the data and the model never leave the same governed boundary to talk to each other.

Built on demand

Need a capability that isn’t here yet? The model writes and deploys it into the same boundary — the catalog is a starting point, not a ceiling.

FAQ

Good to know.

How does this compare to LaunchDarkly?

Progressive delivery and experiments — including flags on model versions and prompts, not just code.

Can I flag a model version?

Yes — roll out models and prompts safely behind flags.

How fast is a kill switch?

Instant — disable a feature without a redeploy.

Deploy anywhere

Your boundary, your choice.

Managed
Your VPC
On-prem
Air-gapped / sovereign

Run Feature flags on Aether Cloud.

Progressive delivery, targeting and experiments with instant rollback. Deployable managed, in your VPC, on-prem or fully air-gapped — talk to us about the configuration your workloads and your boundary require.