The open interface, run for you
AdvertisingOS Cloud is the hosted commercial offering from Surfside: a managed runtime, credential vaulting, SSO, and support — plus four capabilities the open project doesn’t ship. Nothing in Cloud forks the interface: same tools, same schema, same record. The interface stays open and self-hostable.
the logic of the set: cloud is the things an open interface cannot be — a runtime, a data plane, a proof layer, a marketplace. every claim below carries its status.
The open project ships the whole sense–propose–govern–apply loop — recommendations, pacing, anomaly scans — but everything is operator-invoked; nothing runs while your terminal is closed. Cloud is the runtime: triggers and schedules driving the same endpoints, pacing watches and optimization loops that keep working between sessions, team approvals across accounts. Same guardrails, same audit trail — autonomy changes cadence, never governance.
Today the open project ships governed custom-list audiences on every connector that supports audience operations, with identifiers SHA-256 hashed before any network call. Cloud extends that into a data plane: first-party data onboarding, identity, and modeled audiences — rules that build and refresh segments through the same rehearsed, audited pipeline — activated across every connector and on Surfside natively through its Elements audience API.
The open project already returns one report shape from every platform and paces cross-platform flights against a committed plan. What it cannot do is close the loop: a conversion is whatever each platform says it is. Cloud joins delivery to actual transactions on Surfside's measurement infrastructure, so budgets are judged — and optimization loops steer — by revenue rather than platforms grading their own work.
Retailers and marketplaces hold the inventory and the first-party data; Cloud turns them into the sell side. Onsite placements, offsite media, and catalog-linked shoppable experiences on Surfside infrastructure — operated through the same tools, schema, and audit trail as the buy side. The open project ships none of this today, and this page says so until it does.
The build order is public: modeled audiences first, then the hosted runtime, transaction-linked measurement, and sell-side commerce media. It ships in the repo as docs/cloud-roadmap.md and this page tracks it — a capability moves out of “planned” only when the code exists. Pricing is public too: consumption meters, not seats, and rehearsals are free.