Docs
Operations
Keep the program healthy with monitoring, credits, passive-mode awareness, reports, and clear recovery posture when work needs attention.
The dashboard is a signed-in workspace. If you are new, create an account first. If you already have access, continue into the app and pick up the same guide there.
Freshness
Operate monitoring with intent
Monitoring is valuable when it is explicit, narrow, and worth the spend. It should never feel like invisible background drift.
Monitoring principles
Monitoring is opt-in
It should be a deliberate operator choice, not silent background behavior that spends on your behalf.
Route scope matters
Start with a small set of high-value routes so the signal is clear and the spend is proportional.
Cadence should match reality
Choose a schedule that reflects how often the source actually changes and how quickly localized freshness matters.
Change detection should ignore noise
Timestamp churn, consent banners, and boilerplate should not trigger expensive work if the underlying content did not meaningfully change.
Cost model
Monitoring spends 10 units per meaningfully changed page.
If a change requires a new report or regeneration work, plan for 100 additional units.
That is why route scope and cadence matter so much. Monitoring should be justified by the business value of freshness, not by habit.
Billing
Understand spend, headroom, and passive mode
Billing is part of the user experience because it defines how confidently the product can keep doing work.
Starter
$100/month
$100 credit included plus $100 metered of metered headroom.
10,000 included units and 10,000 overage units before passive mode protection is needed.
Growth
$1,000/month
$1,000 credit included plus $1,000 metered of metered headroom.
100,000 included units and 100,000 overage units before passive mode protection is needed.
How billing behaves
Subscription units are spent first
The monthly plan provides the base operating runway for normal launch and maintenance work.
Top-ups extend prepaid headroom
Top-ups are best for launches, spikes, and recovery when the current cycle needs more room but a plan change is unnecessary.
Metered headroom absorbs overflow
Once prepaid units are exhausted, the product can continue within the plan's allowed overage boundary.
Passive mode blocks new AI-bearing work
When the account runs out of safe headroom, the product should prefer predictable pause over surprise spend.
Top-up packs
$25 pack
Adds 2,500 units of prepaid headroom for spikes, launches, and recovery.
$100 pack
Adds 10,000 units of prepaid headroom for spikes, launches, and recovery.
$500 pack
Adds 50,000 units of prepaid headroom for spikes, launches, and recovery.
Review and recovery
Use reports and operator visibility
Operations should give the team clear visibility into what is happening, what is ready, and what needs intervention.
Reports and admin
Reports are launch artifacts
Use reports for review, sign-off, and communication. They should feel editorial and useful, not like system dump files.
Admin is for operator confidence
Use the admin surface to inspect route posture, memory, recovery state, and other advanced controls that should stay explicit and auditable.
Recovery should feel calm
If a route needs retry or review, the product should explain the posture clearly rather than hiding it behind generic failure states.
Operational FAQs
Should I enable every locale we support on day one?
Usually no. Start with one or two high-value markets and widen only after the workflow feels reliable and reviewable.
Can rough content be part of SEO release?
No. Rough can help people, but validated final output is the right bar for crawlable search exposure.
Should I turn monitoring on immediately?
Only if the content changes often enough and the business value of fast localized freshness is already clear.
Do I need structured-content connectors to use the product?
No. The default path is site delivery. Use connectors only when field-level workflows or writeback are actually needed.