Docs
Product Model
Learn the core abstractions that make the product coherent: account, site workspace, brand profile, locale report, approval, delivery snapshot, and more.
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.
Abstractions
The core product model
If the abstractions are clear, the UI and the workflow will feel coherent. If these abstractions are muddy, everything else becomes harder to explain.
Core concepts
Account
The billing and access boundary for your program. Plans, credits, top-ups, and DX expectations all start here.
Site workspace
The core product object. One website plus its active brand profile, approved locales, delivery policy, monitoring plan, and reporting history.
Brand profile
The editorial guidance layer that shapes how translations should sound and what vocabulary must be protected or preserved.
Locale report
A review artifact for a target locale so the team can judge readiness and alignment before widening exposure.
Approval
The operator decision that says a locale is ready to launch under the current policy. Approval is a product action, not a side effect.
Delivery snapshot
The effective live configuration for one site: hostname, default locale, URL strategy, route eligibility, locale policy, and translation profile.
Monitor plan
The optional schedule and route scope for watching source changes and deciding when localized content deserves regeneration.
Connector
An advanced path for structured fields, previews, and writeback when field-level localization matters more than rendered-page delivery alone.
Service boundaries
Rendered delivery path
Use this when you want localized website delivery for visitors. This is the default product path for most customers.
Structured content path
Use this only when the content system itself needs localized entities, drafts, or published writeback beyond rendered pages.
Operator review path
Use reports, approvals, and admin visibility when the release needs stronger oversight than a quick proof-of-concept.
The key mental shift
Do not think in isolated translated strings. Think in one site workspace with governed delivery, brand-aware quality, and locale-by-locale release decisions.
What lives where
How the workspace maps to the app
The app is intentionally organized so the highest-signal decisions remain grouped together.
Home
Paste one URL, choose the first delivery posture, and see the launch runway in one place.
Site
The center of the product. Brand, Locales, Delivery, and Monitoring all live here because they describe one operating system for one site.
Billing
Understand headroom, choose the right plan, add top-ups, and avoid launching into a low-balance surprise.
Reports
Review locale artifacts in a format that can actually support sign-off, discussion, and launch readiness.
Admin
Use advanced controls for route insight, recovery posture, translation memory visibility, and structured-content connector workflows.
How to think about states
The release language you should use
These distinctions matter because they prevent the product from collapsing many different situations into one vague 'done' state.
Generated
Work exists.
Approved
An operator has intentionally released it.
Live
Real users may encounter it under the current policy.
Crawlable
Search engines may index it.