Integrate with MOS
MonetizationOS needs to handle each request to your product to shape the response in return. How you wire that up depends on your platform and what you're building.
Server-side vs client-side integration
| Approach | Best for | Trade-offs |
|---|---|---|
| Server-side: proxy | Static sites, edge-rendered HTML, consistent behavior for users and bots | Requires proxy setup and deployment |
| Client-side: Browser SDK | Rich SPA customization, browser-only interactivity | Depends on JavaScript execution in the client |
We recommend a server-side proxy for most integrations: it enforces response transformation and monetization logic before HTML reaches the browser, without depending on client-side JavaScript. Reach for the Browser SDK when you can't, or prefer not to, put a proxy in front of your origin.
Server-side: proxy integration
MonetizationOS proxies sit in front of your origin, intercepting HTML responses to apply server-side monetization decisions, with no changes to your origin code. Run one at the edge on your CDN, or host it yourself.
How it works
Every proxy implementation follows the same pipeline: fetch the origin response, resolve the user's identity, call the Surface Decision API, and apply personalization transforms to the HTML before it reaches the browser.
To learn more about what proxies are and when to use them, see the Proxies concept page. For a detailed breakdown of the shared proxy pipeline, see the Proxies reference.
Choose your provider
Select your platform below to follow the quickstart guide.
Cloudflare Proxy Worker
Deploy the open-source proxy worker on Cloudflare Workers with one click
Fastly Edge Compute Proxy
Deploy the open-source proxy edge compute on Fastly Edge Compute
Akamai EdgeWorkers Proxy
Deploy the open-source proxy on Akamai EdgeWorkers
Node.js Proxy
Run the open-source proxy core as a self-hosted Node.js service
AWS ECS Fargate Proxy
Deploy the Node.js proxy as a container on AWS ECS Fargate
Build your own
If your platform isn't one of the providers above, build your own proxy on @monetizationos/proxy, the shared core package that powers them.
Client-side: Browser SDK
The Browser SDK runs in your user's browser, makes a surface decision with a public key, and applies the resulting component transformations to the live DOM. Full behavior and configuration live in the Browser SDK reference.