Feature Flag / Config

Ship behind a flag. Tune in real time.
A/B testing & real-time configuration toggles.

Remitgo's config engine puts feature flags, A/B experiments and runtime settings behind a single API. Roll a new corridor out to 5% of one tenant, A/B a fee model, or toggle a module per subscription, and change behaviour instantly, no deploy.

Get API Access View full product
Real-time
No-deploy toggles
A/B
Experiments
Per-tenant
Targeting
Q4 2026
Availability

Feature flags

Wrap any capability in a flag and flip it on or off at runtime, globally, per tenant, per package or per user, without a release.

  • Runtime on/off control
  • Tenant & package scoping
  • Instant propagation

A/B experiments

Split traffic across variants, fee models, onboarding flows, UI copy, and measure conversion and outcome metrics per variant.

  • Traffic splitting
  • Variant assignment
  • Per-variant metrics

Targeted rollouts

Roll a change out to a percentage, a cohort or a single tenant first, then widen the audience as confidence grows. Partial rollouts apply to product behaviour only: compliance-affecting keys are all-or-nothing per tenant.

  • Percentage rollouts
  • Cohort & attribute targeting
  • Product keys only

Runtime configuration

Manage thresholds, limits and module settings as live config, without a code change. Compliance-affecting values (AML thresholds, transfer limits) require a second approver and a recorded justification before they take effect.

  • Typed config values
  • Threshold & limit control
  • Second approver on compliance values

Versioning & rollback

Every flag and config change is versioned with who, what and when, so a bad change is one click away from being reverted.

  • Change history
  • One-click rollback
  • Scheduled changes

Governed & audited

Changes are permissioned per role, carry a written justification and are logged immutably, keeping flag and config control safe in a regulated platform.

  • Role-based change control
  • Immutable change log
  • Per-tenant isolation

API Reference

Integrate in minutes.

Preview of the planned interface - this API is in development and not yet publicly available.

PATCH/api/v1/config/flags/new_payout_corridorPLANNED

Request

{
  "enabled": true,
  "rollout": {
    "strategy": "percentage",
    "value": 5,
    "tenant_id": "tn_3920"
  },
  "effective_at": "2026-10-01T00:00:00Z"
}

Response

{
  "flag": "new_payout_corridor",
  "key_class": "product",
  "enabled": true,
  "rollout": {
    "strategy": "percentage",
    "value": 5,
    "tenant_id": "tn_3920"
  },
  "version": 7,
  "effective_at": "2026-10-01T00:00:00Z",
  "updated_by": "user_admin_2",
  "revert_url": "/api/v1/config/flags/new_payout_corridor/revert",
  "versions_url": "/api/v1/config/flags/new_payout_corridor/versions",
  "api_version": "v1"
}

Compliance-affecting keys (AML thresholds, transfer limits) are changed through PATCH /api/v1/config/values/{key}, which additionally requires justification, approved_by and effective_at. A single caller cannot put such a value live: the change takes effect only after a second approver signs it off. Reverting posts to revert_url with the target version ({ "to_version": 6 }); versions_url lists what can be reverted to.

Decouple release from deploy.

Remitgo launches Q4 2026. Talk to our team about the flags, experiments and runtime config your rollout will need.

Ask about early access Talk to Sales