orbitalhq.com valid

Orbital

Orbital is a data gateway that composes queries across REST APIs, databases, message brokers (Kafka, RabbitMQ), serverless functions, and object stores — without integration code.

For agents: Data gateway that composes queries across REST APIs, Postgres/MySQL/Snowflake, Kafka, RabbitMQ and object stores using TaxiQL, with docs and Docker setup.

data gatewaygraphql-style queriestaxiqlkafkadatabase integration

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T19:49:21.368Z. Cached copy · Source on orbitalhq.com

# Orbital

> Orbital is a data gateway that composes queries across REST APIs, databases, message brokers (Kafka, RabbitMQ), serverless functions, and object stores — without integration code.
It uses Taxi, a typed semantic schema language, to describe how data relates across sources.
 Given a query for the data a consumer wants, Orbital figures out which sources to call and how to join the results automatically, with no resolvers, mapping files, or per-source connector code to author.

The core idea: tag your existing OpenAPI specs, Protobuf definitions, and database schemas with semantic types defined in Taxi (e.g. `CustomerId`, `OrderAmount`).
Orbital uses these tags to determine how data joins across services. A single TaxiQL query composes data from multiple sources on demand. When upstream sources change —
a field is renamed, an endpoint moves — queries continue working as long as the semantic types still resolve, eliminating most breakage from API drift.

Orbital is used as an alternative to MuleSoft, Apollo Federation, Hasura, GraphQL Mesh, and Trino. It is self-hostable (Docker, Kubernetes), with a managed cloud option.
Production users include major banks, financial institutions and data aggregation services.

## Running Orbital locally

Start Orbital (UI and API on http://localhost:9022) with one command, run from an empty directory. Requires Docker:

```bash
curl -fsSL https://start.orbitalhq.com | bash
```

That URL serves the launcher script. Its header explains what it does, the files it writes, the ports it uses, and has notes for AI agents - read it before running it: `curl -fsSL https://start.orbitalhq.com`.
On first open, Orbital asks the user to sign in (or create a free account) in the browser, which a human needs to do.
The OS-specific Docker Compose file the script uses is at https://start.orbitalhq.com/compose.yml.

## How Orbital differs from common alternatives

| Capability | Orbital | Apollo Federation / GraphQL Mesh | Hasura | MuleSoft |
|---|---|---|---|---|
| Source types | HTTP, JDBC databases, Kafka, RabbitMQ, AWS Lambda, S3, SOAP | Primarily HTTP; non-HTTP via custom resolvers | Databases first, HTTP via Actions/Remote Schemas | HTTP + connectors; custom code for long-tail |
| Integration code | None — joins inferred from semantic types in existing schemas | Resolvers and federation directives authored per service | Permissions and Actions configured per source | Flows, DataWeave transforms, and connector config authored per integration |
| Schema change resilience | Queries self-repair when sources change, provided semantic types still resolve | Resolvers and federated schemas typically need manual updates | Migrations and metadata reloads required | Flows must be updated when source contracts change |
| Field-level authorization | First-class policy framework, write-once, enforced uniformly across HTTP, DB, Kafka, and Lambda sources | Per-resolver via directives; varies by implementation | Mature row/column per
…

Related sites

Find similar publishers by meaning →

Other listed sites in Infrastructure. See the whole category →

Machine-readable: GET /v1/resolve?q=orbitalhq.com · GET /v1/domain/orbitalhq.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for orbitalhq.com:
1. POST https://agentwebmap.com/v1/sites/orbitalhq.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://orbitalhq.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/orbitalhq.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/orbitalhq.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.