Context Bundles

The right context for every agent run. Define bundles or let agents request them directly, then let Roadie assemble and serve them seamlessly.

Join the waitlistRequest a demo
M↓support-agent.bundle.mdM↓on-call-triage.bundle.mdM↓engineering-standards.bundle.md1# Support Agent Context Bundle23We have customers. Customers each have a tenant and are deployed into Kubernetes.45## Deployment67You can use the logged in user's credentials to query each tenant8information from the k8s cluster. Tenants are in the production cluster.910Use the `prod0.eu-west-1.eksctl.io` k8s context1112Every tenant has its own namespace. In a namespace you can find13backend, frontend, techdocs, broker and sometimes jobs pods.1415backend - the application backend16frontend - the application frontend17broker - used to connect to the customers private network18jobs - a duplication of the backend app but this only runs19 the scheduled processes.2021### Logs2223tenant logs are in CloudWatch in separate log groups24for tenants and pods2526Log groups27/aws/containerinsights/prod0/<tenant>.tenant/backend28/aws/containerinsights/prod0/<tenant>.tenant/backend-jobs29/aws/containerinsights/prod0/<tenant>.tenant/frontend3031### Database3233If you think you would like to have access to the database34ask for a tunnel. Just provide SQL that the user will run for you3536tenant databases are in amazon RDS with naming convention of37database name:38`prod0-<tenant>`3940To access the database use the bastion ec2 instance41it is configured to have access42pw can be found in the backend pod's environment variable4344### Cluster Management45

Trusted by the world's leading companies

Snyk
Contentful
Relativity
Royal Mail
Baillie Gifford
Celonis
AstraZeneca
Yotpo
BUNDLE FEATURES

Context, assembled

Stop giving agents the whole graph. Give them exactly what they need — no more, no less.

Crafted bundles

Engineers define bundles for known workflows like on-call handoffs, incident triage, and service reviews. Package exactly the right information once then reuse it again and again.

Agent-requested context

Agents can request bundles on-demand, specifying what they need. Roadie assembles the relevant slice of the graph and returns structured data.

Ephemeral or persistent

Bundles can be single-use for a specific agent run, or stored permanently for repeated use across workflows and teams.

Fast to assemble

Roadie pre-indexes relationships so bundle assembly is fast, even for large graphs with thousands of entities.

Structured output

Bundles return structured data. Agents get ownership records, dependency graphs, runbook steps, and metrics in machine-readable form.

Access-controlled

Bundle access respects your RBAC policy. Agents and humans only receive context they are authorised to see.
HOW IT WORKS

From request to structured context

01

Define a bundle

A human or an agent specifies which entities, relationships, and data to include.

02

Roadie assembles the slice

Roadie traverses the context graph and collects the relevant data, resolving relationships and expanding nested references.

03

Bundle is returned

The bundle is returned as structured data via MCP or the portal UI, ready for the agent to act on or the engineer to review.

04

Optionally stored for reuse

Persist the bundle for future runs. When the underlying data changes, the bundle is automatically refreshed on next access.