Edge runtime

Horizon

Ultra-low latency feature flag evaluation and environment config, at the edge of our global network or on infrastructure you run yourself. Your instances answer first, and Hyphen is the backstop.

Toggle · ENV · one container · any region
horizon
checkout-v2 · evaluate
3 instances
Answered by
Self-hosted · us-east-11.2ms
cached locally
Instances
  • us-east-1Self-hosted1.2 ms
  • eu-west-1Hyphen edge4.8 ms
  • ap-southeast-2Self-hosted1.6 ms
Capabilities

Evaluation and config at the edge, or inside your own network.

The same service either way. Where it runs is the part you choose.

  • Edge flag evaluation

    Evaluate feature flags at the edge to reduce latency and deliver faster user experiences, with fewer round trips to the core service.

    About Toggle
  • Environment config delivery

    Horizon serves ENV reads as well as flags, injecting environment variables into your apps with encryption in transit and at rest.

    About ENV
  • Globally distributed

    Hyphen runs Horizon in regions around the world, so low latency and high availability are the starting point rather than something to build.

  • Fault-tolerant design

    Local caching and fallback handle outages and network instability gracefully, so instability degrades the path and not the answer.

  • Lower latency, on purpose

    Deploy Horizon close to your users or services for faster evaluations and variable delivery, especially in regions where cloud latency is the problem you are solving.

  • Resiliency with failover

    Self-hosted instances stay operational even if the primary service is unavailable, which keeps flags and environment variables reachable throughout.

  • Unlimited redundancy

    Run as many instances, in as many regions or environments, as you need. Each runs independently and stays in sync, so a backup is always ready.

  • Cached hard

    Repeat evaluations are served from the instance's own cache, which is what keeps it answering through a partition and keeps your usage down.

Self-hosting

One public image. Run it wherever your services already run.

Create an API key in the Hyphen app under Settings, grant it project collaborator access to the projects the instance will serve, and start the container. It listens on 3333 and respects $PORT, so Cloud Run and Azure Container Apps both take the image as it is.

Self-hosting guide
docker run -e API_KEY={your_key} -p 3333:3333 us-docker.pkg.dev/hyphenai/public/horizon:latest
API_KEYrequired
Authenticates the instance with Hyphen. Give it project collaborator access to every project the instance will serve.
HYPHEN_BASE_URLoptional
Only when Hyphen has given you a URL of your own. Left unset, the instance talks to the public service.
Coverage

One instance, both services. Anywhere a container runs.

Your flags

Evaluations return the same answer at your edge as they do at ours, with the same targeting rules and the same segments behind them.

About Toggle

Your config

Environment config is served alongside the flags, so one instance covers both of the things an app needs before it can start.

About ENV

Your clouds

Cloud Run, Azure Container Apps, your own cluster, or a laptop for a smoke test. It is one public container image everywhere.

Deployment options

Put evaluation next to your workload.

Start on Hyphen's edge, then run instances of your own where the milliseconds matter. Same flags, same config, one API key.