Platform

The platform

An open execution platform for programmatic media.

Models make decisions in the bid stream. Always-on agents manage everything around them.

Bring your own, use ours, or combine both.

SYSTEM 2 · AGENT SYSTEM 1 · BID STREAM MILLISECONDS
( 01 / 12 ) Architecture

Two systems. Different jobs.

Media buying needs two very different kinds of intelligence.

System 1

Fast decisions, inside the bid stream.

Every impression requires a decision in milliseconds.

System 1 models run directly in the buying path and answer questions like:

  1. 01Is this impression valuable?
  2. 02How likely is it to convert?
  3. 03What is it worth?
  4. 04Is this inventory high quality?
  5. 05How much should we bid?
  6. 06Should we bid at all?

These models are small, fast and purpose-built.

They do not need to reason about an entire campaign. They need to make one decision extremely well.

System 2

An always-on agent managing the campaign.

Campaign management happens over minutes, hours, days and weeks.

System 2 is a persistent agent that stays with the campaign throughout its life.

It can:

  • monitor performance
  • investigate changes
  • adjust budgets
  • launch experiments
  • compare models
  • retrain models
  • change targeting
  • diagnose underdelivery
  • review supply
  • generate reports
  • ask for approval when required

Use the agent built into the platform, or bring your own.

( 02 / 12 ) Agents

Manage campaigns from Claude or ChatGPT.

The entire media platform is an API.

Agents are native operators.

You should not need to live inside another adtech dashboard just to manage a campaign.

Connect your own Claude, ChatGPT or agent environment and tell it what you want.

For example:

Instruction
Check this campaign every weekday morning. If CPA moves more than 15%, investigate why. Make small budget adjustments automatically. Ask me before changing models or increasing total spend.

Or:

Instruction
Test the new store-visit model against the current model. Keep 80% of spend on the existing model. Move more traffic only if the new model performs better.

Schedules, guardrails and approvals remain explicit.

The agent keeps running even when you are not talking to it.

( 03 / 12 ) Models

Open AdTech System One Models

We are building an open family of models specifically for media decisioning.

Think of it as the beginnings of a Hugging Face or PyTorch ecosystem for programmatic decisioning.

  1. Start with an open model.
  2. Train it on your own data.
  3. Fine-tune it.
  4. Evaluate it.
  5. Deploy it directly into the bid stream.

Initial model families include:

  • conversion propensity
  • click propensity
  • attention
  • inventory quality
  • contextual relevance
  • store visits
  • bid pricing
  • win probability
  • incremental lift
  • carbon efficiency

Every model comes with the code, training recipe, evaluation approach and deployment format needed to actually use it.

( 04 / 12 ) Training

Train and fine-tune on your own data.

Open models are only the starting point.

Use the platform to train or fine-tune them against your own campaign and outcome data.

The workflow is designed to cover the full model lifecycle:

  1. 01Data
  2. 02train
  3. 03evaluate
  4. 04replay
  5. 05shadow
  6. 06deploy
  7. 07monitor

You can compare models against historical auctions before putting spend behind them.

  1. Then run them in shadow mode.
  2. Then send a small percentage of traffic.
  3. Then scale.

Your data and trained models remain yours.

( 05 / 12 ) Composition

Models are composable.

There should not be one universal media algorithm.

Different models can contribute different pieces of the decision.

For example:

Attention model × Conversion model × Inventory quality model × Price model = Bid decision

Different participants can contribute different models.

A model might belong to:

  • an advertiser
  • an agency
  • a publisher
  • a data provider
  • an independent developer
  • the open-source community

The platform provides a common way to run them together.

( 06 / 12 ) Marketplace

A marketplace for media intelligence

Models are portable assets.

AgencyAn agency can build a model and use it across its clients.
AdvertiserAn advertiser can keep a proprietary model private.
PublisherA publisher can expose a model describing its inventory.
DeveloperA developer can release an open-source model.
SpecialistA specialist can charge for access to one.

The platform handles how those models are discovered, combined, evaluated and executed.

The intelligence belongs to whoever created it.

( 07 / 12 ) Open source

Open auction infrastructure

The core auction server is open source.

  • No hidden bidder.
  • No private decisioning layer.
  • No requirement to trust us about what happened in the auction.

Developers can inspect the code, run it themselves, contribute to it or build their own infrastructure around it.

Our managed platform runs the same open core.

( 08 / 12 ) Deployment

Containers are the deployment unit.

Buying logic should be portable.

A model or bidder can run close to the auction rather than every opportunity travelling through layers of external infrastructure.

The same workload can move between supported execution environments without being rewritten.

Containers make that possible.

They also make ownership clear: your logic is an actual deployable piece of software, not a setting hidden inside someone else's platform.

( 09 / 12 ) Logs

All your logs. No logging tax.

Every decision should be inspectable.

You get access to:

  • auction opportunities
  • features used
  • model versions
  • model scores
  • bid decisions
  • clearing prices
  • wins and losses
  • campaign changes
  • agent actions
  • experiments
  • outcomes

The logs are yours.

There is no additional fee to access your own event history or export it elsewhere.

( 10 / 12 ) Efficiency

Efficient by design

Programmatic infrastructure processes enormous volumes of data.

That makes efficiency matter.

We want the real-time path to do as little unnecessary work as possible.

Waste less compute → lower cost → lower latency → lower carbon

Those goals reinforce each other.

The core execution layer is designed around that principle from the beginning.

( 11 / 12 ) Supply

Direct publisher supply

We want a clear path between buyer and publisher.

That does not mean every publisher must integrate directly with us.

It means avoiding unnecessary hops, reselling and duplication wherever possible.

Every impression should have understandable provenance.

( 12 / 12 ) Developers

Built for developers too

For developers, one way to think about the platform is:

Cloudflare Workers for RTB + Hugging Face for buying models + an agentic control plane

A fast execution environment.

An open model ecosystem.

And an always-on system capable of operating campaigns on top.

( Open source )

Open from the beginning.

The aim is not to build another closed media platform.

It is to create infrastructure that agencies, advertisers, publishers and developers can build their own media systems on top of.

Join the waitlist