Conductor runs on your own infrastructure. You can run it as a binary or in a containerized environment like Kubernetes or Docker. You can also run Conductor as a CloudFlare Worker (WASM-compiled).
We handle all the complexities under the hood to support Apollo Federation including query planning, steps execution, parallelization and response merging. (Fusion support is also on the way!)
Expose the same or different GraphQL sources(s) on multiple endpoints: each endpoint can have its own flow and plugins.
Easily fork Conductor, and add new custom plugins for your own, that fits your use. Our plugins architecture is easily extended. And you can always pull request your custom plugins if you think can be broadly beneficial.
Connect single or multiple caching stores, and simply plug-in caching to your GraphQL services. We support in-memory, redis and CloudFlare KV stores.
Built-in plugins for popular authentication flows (JWT with JWKS). Also, hardening plugins like rate-limit are available.
Monitor your service with built-in support for telemetry (OpenTelemetry, Jaeger, DataDog).
Yes. Conductor is a drop-in replacement for Apollo Router, please open issues on our github repository if you face any unexpected behavior.
Conductor offers all of the Enterprise features you expect from other gateways at no cost. We have Authentication, Caching, and Open Telementry plugins that are extremely easy to use.
It should be! Our tools are built to be agnostic and vendor-free, you can choose and mix between our tools and others tools like Apollo Studio, Uplink or GraphQL Hive for example.
Of course! Our roadmap is publically published, you can open new issues for requested features or report bugs, you can tell us if we need to reprioritize our roadmap, open pull requests.