Tailcall, an open source GraphQL gateway that composes your REST, gRPC and GraphQL services into a single unified GraphQL API from one declarative configuration.
Tailcall is an open source GraphQL platform that turns existing REST, gRPC and GraphQL services into one unified GraphQL API. Instead of writing resolver code, you describe how to compose your upstreams with a small set of declarative schema directives: a field can be backed by a REST endpoint, stitched from another GraphQL or gRPC service, computed by an offline expression, or chained through a prior query, and the gateway resolves each field by calling the right upstream while batching and caching requests to keep things fast. The whole API is defined in one readable schema file, so the shape of your graph and the way it maps onto your services live side by side and are easy to review and change.
It suits teams that want a single, consistent GraphQL surface over a sprawl of internal and third party services without standing up a bespoke backend for frontend, engineers modernising a REST estate behind a typed graph, and anyone who needs a fast, declarative API gateway they run and own themselves. Because behaviour is driven entirely by configuration, the same binary serves anything from a thin proxy over one API to a rich graph stitched across many.
cloudimg delivers Tailcall fully installed as a single self contained native binary, run as a dedicated non root service bound to the loopback interface and exposed only through an nginx reverse proxy that is ready for your TLS certificate, so a working GraphQL endpoint answers the moment the instance boots. It ships with a starter configuration that composes a public sample REST API into GraphQL, so you can send a real query immediately and then replace the configuration with your own upstreams and restart the service. Because the shipped gateway fronts only a public demo API and defines no admin interface and no secret, the image honestly carries no baked or shared credential, and any secrets your own upstreams need are supplied by you at runtime rather than built into the image. Each instance resolves its own public endpoint URL on first boot, the base is fully patched with unattended security upgrades enabled, and every deployment is paired with a step by step deploy guide and 24/7 cloudimg support.