A hosted home for scheduled agents — bring your AI key, connect your data, pick recipes from the catalog. Cron-driven workers in your cloud, no glue code. Logs and run history in your account, not ours.
Every module is a fixed shape. We deploy it into your cloud, hand over the keys, and step out of the room.
Recipes are real, named workflows — revenue snapshot, support digest, inventory alert, refund anomaly. Each one has been built and tested in an actual operation.
Per-source OAuth flow for the upstream systems each recipe needs. Your Anthropic API key (or your enterprise Bedrock / Vertex deployment). All credentials sit in your environment, scoped to the recipe.
Recipes run on the schedule you set. Run history, structured logs, output artifacts — all in your account. We provide the runtime, you keep the data.
The capabilities that make this module the right shape, not just the right name.
Real workflows, not blank-page templates. Each recipe ships with sane defaults.
Per-source consent. Granular scopes. Revoke at any time without breaking everything.
Run history, structured logs, output artifacts — sit in your project, not ours.
Anthropic API, AWS Bedrock, Google Vertex — wherever your enterprise key lives.
Recipes pin to a version. Updates are explicit; you choose when to bump.
Bring a recipe we don't have. Field Office runs it the same way as the catalog ones.
A module joins the catalog only after the same shape has been built three times for three different operators. Here's who those were.
You shouldn't need to maintain a cron server to get a daily report posted to Slack.
Below the team size where building a hosted agent runner makes sense.
If you've described the dream as 'cron, but for Claude' — this is that, with the safety rails.
If you have a question that isn't here, that's also fine — bring it to the call.
Planned for late 2026. The runtime is being battle-tested through the Pulse and Almanac engagements right now — Field Office is the productization of that runtime.
A YAML definition naming a schedule, sources, model, prompt template, and delivery surface. The same shape we use for bespoke scheduled agents today.
Yes. The recipe spec will be public. You can write, share, and version them like any config artifact.
Different shape. Zapier and n8n are great for trigger-based glue between SaaS apps. Field Office is for cron-driven, AI-mediated reasoning over your warehouse — a different problem.
A 30-minute call. No deck, no demo — just the work. If Field Office is the right shape, we'll say so. If not, we'll point at one that is.
Book a call →