Integrations
Orchestrator is positioned for running CloudX alongside other mediation platforms, with ad unit level control from the dashboard. No named partner list is published on the homepage.
Learn moreCloudX
Programmatic ad stack for mobile publishers, run by an AI agent
Advanced
What is CloudX?
CloudX is a supply side platform for mobile publishers that combines ad serving, a TEE based auction, dynamic pricing, analytics and a beta monetization agent that can adjust price floors, build line items and run scheduled checks from natural language prompts.
CloudX is a supply side platform aimed at mobile publishers who want control over their own ad inventory. It bundles the pieces a publisher normally assembles from several vendors: ad serving, a real time auction, dynamic pricing, feature level analytics and a mediation layer. The distinguishing piece is a monetization agent, currently in beta, that reads your inventory data and acts on it. Ask why eCPM fell and it investigates; ask it to raise price floors by 15 percent across banner line items in your gaming apps and it locates the affected items, reports the tier by tier change and stages the update. The practical audience is app developers and monetization leads running portfolios of games or utility apps, particularly smaller teams without a dedicated ad ops analyst. Day to day work happens through a dashboard that shows earnings, impressions, fill rate, requests and revenue per active user alongside placement level breakdowns. The agent can also operate on a schedule: a task is described once, given a run time, and returns results in chat or by email. The Orchestrator lets CloudX run beside other mediation platforms, with ad unit level decisions made from the dashboard rather than shipping a new app build. Under the hood, sellers integrate an SDK, define placements and placement groups in configuration (line items, formats, bid response and ad load timeouts), and let agents create line items and deals. The company describes its auction as TEE based (trusted execution environment), a design choice positioned at unlocking more demand. Machine learning based dynamic pricing prices individual ad requests rather than applying one static floor. Compared with established mediation and SSP suites, CloudX is early: the agent is labelled beta, documentation is thin on the public site, and pricing is not published. Publishers comfortable testing newer infrastructure, and especially those already automating internal workflows, get an agent native toolset; conservative ad ops teams may prefer to wait for the agent to leave beta.
How do you use CloudX?
1Review what the platform covers
Read the homepage overview to understand the stack: ad serving, auction, dynamic pricing, analytics and the agent. Note that the agent is in beta before planning a rollout.
2Integrate the CloudX SDK
Follow the SDK post to add CloudX to your app and confirm that impressions and requests start reporting against your apps.
3Define placements in configuration
Set up placement groups and placements (banner, timeouts, native templates) in the config format shown on the site, then verify they appear in the dashboard.
4Put the agent to work
Open the agent and ask a specific question, such as which demand partner is taking the most impressions at a low eCPM, or request a price floor change and review the proposed update before applying it.
5Schedule recurring checks
Once a useful prompt is found, turn it into a task with a run time so results arrive in chat or by email on a schedule.
6Run beside existing mediation
Use Orchestrator to decide, ad unit by ad unit, how CloudX works with your other mediation platforms, without shipping an app update.
Pros and cons
Pros
- Agent handles concrete monetization work such as adjusting price floors and preparing A/B experiments, not just answering questionsAI
- Scheduled tasks deliver recurring monetization checks by chat or email without manual dashboard visitsAI
- Orchestrator lets CloudX coexist with other mediation platforms, decided ad unit by ad unit from the dashboardAI
- Configuration is code driven (placement groups, line items, timeouts), which suits teams that manage apps as repositoriesAI
- Dashboard covers earnings, fill rate, eCPM, impressions and revenue per active user in one viewAI
Cons
- The monetization agent is still in beta, so behaviour and output should be verified before it touches live inventoryAI
- Public site offers no pricing, no rate card and no details on commercial terms or revenue shareAI
- Documentation on the homepage is mostly feature teasers; deeper SDK, auction and integration specifics require the blogAI
- No published list of demand partners or integrations beyond the other mediation platforms Orchestrator referencesAI
- TEE based auction and dynamic pricing are described qualitatively with no benchmark data to compare against established SSPsAI
How much does CloudX cost?
Features
Features named on the homepage: a full programmatic stack for mobile, a beta monetization agent that creates line items and deals and adjusts price floors, TEE based auction, machine learning dynamic pricing per ad request, feature level analytics with a fast dashboard, monetization as code configuration, scheduled agent tasks, and Orchestrator for running CloudX alongside other mediation platforms.
Learn moreFrequently asked questions about CloudX
How do you use CloudX?
The walkthrough on this page covers 6 steps: 1. Review what the platform covers 2. Integrate the CloudX SDK 3. Define placements in configuration 4. Put the agent to work 5. Schedule recurring checks 6. Run beside existing mediation.What platforms does CloudX support?
CloudX is available on Web App.What does CloudX integrate with?
Orchestrator is positioned for running CloudX alongside other mediation platforms, with ad unit level control from the dashboard. No named partner list is published on the homepage.What are the limitations of CloudX?
The monetization agent is still in beta, so behaviour and output should be verified before it touches live inventory. Public site offers no pricing, no rate card and no details on commercial terms or revenue share. Documentation on the homepage is mostly feature teasers; deeper SDK, auction and integration specifics require the blog.
