Make the budget part of the decision.

Coordinate budget reservations, pacing and frequency caps. Decide whether to participate before committing to the next opportunity.

See how it works
Integer moneyBudget reservationsFirst-price shading

Coming soon. Request early access.

Budgets and pacingExample
Remaining$680Illustrative budget
Spent
$320
Reserved
$120
Available to reserve
$560
Participation still follows the pacing plan
Interactive example with illustrative data.

Follow the money through the bid lifecycle.

  1. Check participation.

    Pacing and frequency-cap checks help decide whether an eligible line item should participate now.

  2. Reserve at the final price.

    The ledger checks campaign and line-item accounts and reserves the bid cost before the response is emitted.

  3. Settle from the outcome.

    A billable event commits spend. Losses or reservation expiry release the hold under the configured lifecycle.

Keep buying controls close to execution.

Represent money precisely.

Core money values use integer micros. Protocol conversions sit at the boundary instead of spreading floating-point amounts through the ledger.

Pace against the flight.

Controllers adjust participation using spend and traffic inputs. The ledger and pacing state remain available for inspection.

Respect the privacy decision.

User-level caps apply only when processing is allowed. Multi-bidder deployments use time-limited budget leases to allocate spending authority.

How is spending authority shared across bidders?

The control plane grants time-limited budget leases. Each bidder uses its local authority for reservations and stops when that authority is spent or expired. The split-role integration test covers bidding under a lease and forwarding delivery back to control.

Switch to a modern,
affordable DSP.

Buy programmatically or go direct, with agentic workflows and validation included.

Get early access.

Leave your email. We’ll be in touch when pico DSP is ready.

Only pico DSP launch and early-access updates.