Open source, Go, Apache 2.0

RTB platform,
as code.

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

One model for every RTB flow.

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: split
flow
  1. entry1.2k in640 resp
  2. normalizer1.2k in640 resportb-httportbyour-decoder
  3. module1.2k in180 filteredortb-validationgeo-protectionyour-logic
  4. router1.0k in640 respmediatype-isyour-rule
  5. splitter1.0k in640 resphighestbidyour-reconciler
  6. caller1.0k in640 resportb-jsonyour-encoder

Atoms

  • entry
  • normalizer
  • module
  • router
  • splitter
  • caller

Quarks of module

  • ortb-validation
  • geo-protection
  • your-logicGo

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

Stop rebuilding the same 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.

  • BiddersDSPs and SSPs you send bid requests to
  • CuratorsCurated supply and deals
  • Data vendorsAudience and contextual signals
  • Identity providersUser IDs and identity resolution
  • Measurement providersViewability and attention
  • Ad qualityCreative scanning, brand safety, fraud
  • ComplianceConsent, privacy signals, regulations
  • OptimizationTraffic shaping, dynamic floors, smart repackaging, bidder boosting
  • Any tech vendorAnything else your flow calls

One molecule per integration

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.

Inside a molecule

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

bidder adapterone block, ready-made
molecule
splitterby-mediatype
routermediatype-is
callervideo
callerbannernative

One call per endpoint

  • videobidder.example/video
  • bannernativebidder.example/display

With the bidder's own encoder and decoder.

Industrialize operations

Run your flows like any other service.

A flow is production software, not a black box: you read it, review it, measure it and replay what it did.

Flows as code

A flow is a YAML file in your Git repo, reviewed like any config. An invalid flow doesn't start.

Monitoring

Counters on every atom, in impressions: what comes in, what is filtered and why, what comes back. Exported as OpenTelemetry to your backend.

Data collection

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

Fit it to where you are.

Embed it or run it as a service, and adopt it at your own pace, inside the stack you already run.

Two ways to run it

In your Go code, or as a service beside any stack.

Library

Embed it in your Go service

The main road: your code calls the flow's entry point and it runs in your process, with no network hop.

Standalone

Run it as a service

A provided binary serves your flows over HTTP to any stack. Custom quarks? Build your own binary.

Headless

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

  • Logs
  • Metrics
  • Error spans
OpenTelemetry
  • Datadog
  • Tsuga
  • Any OTel backend

Four ways in

From a blank page to a platform you take over.

  1. 01
    StartNew platform? Skip the plumbing, start with flows.
  2. 02
    ExpandRunning one? Add flows and integrations beside it.
  3. 03
    RefactorMove legacy code into flows, one at a time.
  4. 04
    AbsorbBring another platform's flows under the same model.

What it needs

Besides Go and your bidders, two services in your own infrastructure.

  • An OpenTelemetry backendrecommended
  • A cloud storage bucket in your accountrequired

Trust

Open by license, yours by design.

The framework carries the plumbing. Your logic, your flows and your data stay yours.

Apache 2.0

The same license as Prebid Server, Airflow and Kestra.

  • Use it
  • Modify it
  • Embed it
  • Ship it

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.

See if Rutabago fits your stack.

Tell us what you run.