Declarative API integration

Add tags to your APIs.

Use the same tags to query and mutate data.

Orbital builds and maintains integrations automatically.

No manual glue code. No breaking changes.

Traditional integration

Write custom code for each integration and pipeline
Repetitive work across projects
Breaks whenever systems change
Complex deployment and infrastructure to manage

With Orbital

Embed semantic tags in your APIs and schemas
Queries and mutate data using the same tags
Automatic updates as APIs evolve
Serverless deployments right from git

Code

Effortless integration

Orbital's declarative language - TaxiQL - lets you focus on what you need to get done, rather than boilerplate glue code.

Beautiful, declarative orchestration

TaxiQL let's you describe orchestrations in a declarative, human-readable way.

Using the same tags embedded in your schemas, Orbital instantly creates even the most complex integrations

Learn more

Powerful developer tooling

Design, debug and iterate your integrations in our powerful browser editor.

Get fine-grained call tracing, end-to-end lineage and detailed observability data, so you can see exactly what's going on.

Powerful type checking for fewer errors

Taxi and TaxiQL provide end-to-end type safety across all your data sources, APIs and Kafka topics

Learn more about Taxi, our open source schema language

VS Code extension

Auto-completion, linting, formatting, and inline documentation helps developers build and ship directly from within VSCode

Install the Taxi VSCode extension

Use cases

Unify your whole stack

Connect any combination of APIs, databases, streams and batch sources without writing integration code. Orbital handles all the complexity - no resolvers, YAML mapping files, or integration code to maintain.

Keep your team shipping features, not building glue-ware.

// Send a query for data to Orbital,
// and it builds the integration on demand,
// using metadata embedded in your API specs
find { Movies(ReleaseYear > 2018)[] }
as {
   // Consumers define the schema they want.
   // Orbital works out where to fetch data from
   title : MovieTitle // .. read from a db
   review : ReviewScore // .. call a REST API to find this
   awards : AwardTitle[] // ... and a gRPC service to find this.
}

Try this example in Taxi Playground

Unify your APIs and data sources

// Send a query for data to Orbital,
// and it builds the integration on demand,
// using metadata embedded in your API specs
find { Movies(ReleaseYear > 2018)[] }
as {
   // Consumers define the schema they want.
   // Orbital works out where to fetch data from
   title : MovieTitle // .. read from a db
   review : ReviewScore // .. call a REST API to find this
   awards : AwardTitle[] // ... and a gRPC service to find this.
}

Try this example in Taxi Playground

ETL pipelines

// Define simple schemas for CSV files, then
// read from S3, databases, or upload directly to Orbital
@Csv
closed model InventoryReport {
  name: ProductName
  category: Category
  stock: StockLevel
  price: Price
}

Try this example in Taxi Playground

Event streaming and enrichment

// A stream of data over Kafka
@KafkaService
service FilmReviewUpdates {
    stream reviews: Stream<NewReviewSubmittedEvent>
}

// Stream data from Kafka, and enrich it
// from APIs:
stream { NewReviewSubmittedEvent } as {
    id: FilmId // From the event
    title : Title // Looked up from a DB
    reviews: Review[] // Fetched from an API call
}[]