Flows as code
A flow is a YAML file in your Git repo, reviewed like any config. An invalid flow doesn't start.
Open source, Go, Apache 2.0
Rutabago is an open-source Go framework for RTB flows: declared in YAML, extended in Go, with reusable integrations and built-in monitoring and data collection. It runs in your stack, and what you build stays yours.
In active development. Access on request.
Standardize development
Every platform invents its own way to describe a flow, and every new hire learns it from scratch. Rutabago gives you one model, small enough to hold in your head.
flow.yaml
1atoms:2 - id: in3 type: entry4 - id: norm5 type: normalizer6 - id: checks7 type: module8 quarks:9 - ortb-validation10 - geo-protection11 - your-logic12 - id: route13 type: router14 target: splitAtoms
Quarks of module
built-in yours
The path of a request, from entry to bidder call, as a chain of atoms.
The framework's building blocks: entry, normalizer, module, router, splitter, caller. You chain them, you never modify them.
Your business logic in Go, inside an atom. Built-in or your own.
Commoditize integrations
Every platform integrates the same partners, then does it again at each spec change. That work differentiates no one. Rutabago makes it a shared, maintained commodity.
Every integration is a molecule: a ready-made group of atoms that packages a vendor or a shared capability like compliance, maintained by the vendor or the Rutabago community. Add it to your flow and the integration is in place.
A bidder adapter split by media type: one block in your flow, four atoms inside, one call per endpoint. Need something unique? Write quarks. Reuse atoms. Configure molecules.
In your flow
One call per endpoint
With the bidder's own encoder and decoder.
Industrialize operations
A flow is production software, not a black box: you read it, review it, measure it and replay what it did.
A flow is a YAML file in your Git repo, reviewed like any config. An invalid flow doesn't start.
Counters on every atom, in impressions: what comes in, what is filtered and why, what comes back. Exported as OpenTelemetry to your backend.
Payloads, requests, calls and impressions land as Parquet in a bucket you own. You decide who reads them: your teams, your tools, your vendors.
How to use it
Embed it or run it as a service, and adopt it at your own pace, inside the stack you already run.
In your Go code, or as a service beside any stack.
Library
The main road: your code calls the flow's entry point and it runs in your process, with no network hop.
Standalone
A provided binary serves your flows over HTTP to any stack. Custom quarks? Build your own binary.
No screen, by design. You drive Rutabago from a CLI and watch it in the observability stack you already run.
Drive it
$ rutabagoA CLI ships with the framework.Watch it
From a blank page to a platform you take over.
Besides Go and your bidders, two services in your own infrastructure.
Trust
The framework carries the plumbing. Your logic, your flows and your data stay yours.
Your quarks and flows are your intellectual property. Apache 2.0 puts no obligation on them, and you publish nothing.
They live in your repo and run in your own infrastructure.
Written to a bucket in your own account. You decide who reads it.
The same license as Prebid Server, Airflow and Kestra.
Commercially, without asking us. Every released version stays Apache 2.0.
Built by people who've run RTB platforms. Ten years of building and running an SSP, and paying for the plumbing more than once.
Tell us what you run.