Proxies

A proxy runs in your edge-compute capable CDN in front of your origin server and applies MonetizationOS Surface Behaviors before content reaches end users. They are a strong fit for static HTML sites and edge-first architectures where server-side transformation is preferred over browser-side execution.

Why proxies?

Use a proxy when you want monetization behavior enforced as part of the response path at the edge.

• Apply decisions consistently for users and bots
• Protect content before it reaches the browser, reducing risk of client-side circumvention
• Leverage edge compute for low-latency decisioning and response transformation
• Reduce client-side dependency for core paywall or messaging behavior
• Centralize business logic across web and API surfaces in Surface Workflows
• Keep application code changes minimal for static and multi-origin sites
• Utilize the bot detection features of your CDN to protect content and optimize delivery

Current providers

All MonetizationOS proxy integrations are open source and self-hosted by customers. This gives you full control over configuration, deployment, and customization, while we provide reference implementations and guidance to streamline development.

Server-side vs client-side integration

CDN proxies represent the server-side integration path. Instead of waiting for browser JavaScript to initialize and mutate page content, transformations happen as part of the edge response lifecycle.

Choose server-side proxies when deterministic delivery and minimal client footprint are priorities. Choose client-side integration when you need rich in-browser interactivity tightly coupled to your frontend runtime.

Learn More

Getting Started guides

References

Proxy references

API references

Workflow references

Admin Guides