WaymakerOS is not a container platform
Ambassadors are request- and schedule-scoped: they wake, do the work, and shut down. If you need a process that stays resident, this is the wrong platform and no configuration will change that.
Use these instead
- Fly.io — long-running processes close to your users, with persistent volumes.
- Railway — the least friction for a container that simply needs to stay up.
- Render — background workers and managed services with straightforward operations.
- Kubernetes — when you genuinely need orchestration, and you will know if you do.
Each invocation here is independent. There is no process that persists between requests, no in-memory state carried across invocations, and no way to hold a connection open indefinitely. That is a property of the execution model rather than a limit we intend to raise.
Workloads that do not fit, stated plainly: real-time multiplayer game servers, bot runtimes holding persistent socket connections at scale, video transcoding pipelines, data-warehouse ETL jobs measured in hours, and long-lived agent runtimes that must stay resident between turns.
If any of those describe your workload, use one of the platforms above. We would rather you succeed elsewhere than have you discover the boundary two weeks into a build.
What fits here
- —Webhooks — receive, process, respond, stop.
- —Scheduled jobs — the nightly report, the weekly sync, the hourly check.
- —AI agents that complete a single task per invocation rather than staying resident.
- —Internal tools and business automations that read and write your own data.
Frequently asked questions
- Can WaymakerOS run long-running processes?
- No. Ambassadors are request- and schedule-scoped: they wake on a trigger, complete the work, and shut down. Anything needing a resident process — a persistent socket, an in-memory queue, a worker that stays up between jobs — belongs on a container platform such as Fly.io, Railway or Render.
- Can you run a WebSocket server on WaymakerOS?
- Not as a persistent connection you own at scale. The execution model assumes an invocation begins and ends. Real-time systems holding many simultaneous long-lived connections are a container or dedicated-infrastructure workload, and trying to force them here produces a fragile result.
- What is the practical limit on an Ambassador?
- They are designed for work measured in seconds rather than hours — a webhook, a scheduled job, a single agent task. If your job routinely runs for a long stretch or needs to resume where it left off, that is a signal to move it rather than to optimise it here.
- What workloads is WaymakerOS actually best at?
- Work that is short, triggered, and needs your business data. Webhooks, scheduled jobs, AI agents completing one task, and internal automations. The advantage is not raw execution — it is that the function starts with the database, AI and identity already in scope.
If your workload fits, this is a tighter platform. If it does not, use the right tool — we would rather you succeed.