Observability

See exactly what happened

Orbital records every integration as it runs - the plan, the services called, and where each value in the result came from.

Tracing and lineage are built in. No instrumentation required.

Observability

Be in the room where it happened

Orbital builds and runs the integration, so tracing comes built in. Every call, transformation and result is captured automatically.

Tracing

Follow a request across every database query, API call and service invocation, with timings, inputs and outputs for each step.

See the exact path Orbital took to produce the result.

Lineage

Trace any value in a result back through the operations and transformations that produced it, all the way to its source.

Essential for debugging complex integrations and proving regulatory compliance.

Observability

Track latency, throughput and errors across the services involved in each integration.

Find the slow call or bottleneck without reconstructing the path yourself.

Architecture

Orbital builds service and data-flow diagrams from the integrations it executes.

See which systems depend on each other and how data moves between them, based on runtime behaviour rather than a diagram someone has to keep updated.

Use cases

Whether you’re troubleshooting an integration or proving regulatory compliance, Orbital shows you exactly how your data flows.

Got another gnarly question? We’d love to hear it. Come and chat on Slack.

: Orbital acts as a proxy for your service calls, naturally capturing timing and payload data as requests flow through the system.
There’s no code instrumentation required and no performance overhead on your services - we simply observe the interactions that are already happening.
: While traditional catalogs rely on static analysis and manual documentation to guess at data flows, Orbital captures what actually happens at runtime.
Every service call, transformation, and calculation is automatically recorded, giving you a precise, up-to-date view of how your data moves and changes.
This eliminates months of documentation effort and removes the need for a separate lineage system - saving both significant time and licensing costs.
You get better data lineage as a natural byproduct of your integrations.
: Yes - Orbital’s runtime lineage is specifically designed for regulatory compliance.
For every value produced by Orbital, we automatically capture the complete chain of evidence: which services were called, what transformations were applied, and how the final value was calculated.
Instead of spending months documenting flows and maintaining a separate lineage system, you get audit-ready evidence automatically.
This dramatically reduces compliance overhead while providing more accurate, trustworthy data for regulations like BCBS 239.

Every API call, every transformation applied, every value traced back to its source.