Scattered content
Pages, assets and translations live in separate tools.
Build pages, organize content and work across languages in one CMS. Connect your frontend, review changes and publish on your terms.
Pages, assets and translations live in separate tools.
A form alone does not show the page you are building.
A new language should not mean rebuilding your structure.
Your content should outlive the next website redesign.
Define fields and relationships in TypeScript or create collections in the admin. Give every piece of content a structure.
Explore content modelsBuild pages from blocks, prepare localized content and organize media. Altovar AI can help with drafts when configured.
Try the editorCheck the preview, review changes and keep a version history. Advanced approval and scheduling follow eligible plans and configured workers.
Explore team workflowsRead published content through the APIs or first-party clients. Signed webhooks connect publishing to the build or workflow you configure.
Build with OspreySee how content usage relates to your plan. The animation is an illustrative allowance, not live workspace data.
↗Five workspace roles and scoped, expiring API keys keep access explicit. Advanced permissions follow plan eligibility.
↗Keep authorship, access and change history in view as your content operation grows.
Read published content with the TypeScript client. Use Astro and React integrations or connect your own stack through the APIs.
Explore developer tools1import { OspreyClient } from '@osprey/client'23const osprey = new OspreyClient({4 baseUrl: 'https://cms.altovar.net',5})67const { data } = await osprey8 .collection('blog-post')9 .listEntries({ locale: 'en', limit: 10 })Build landing pages from reusable blocks. Keep media, SEO and translated copy beside the content your team publishes.
ExploreMARKETING TEAMSStructure articles, manage translation coverage and prepare changes with previews and revisions.
ExploreEDITORS & PUBLISHERSDefine a schema in TypeScript and deliver published entries to Astro, React or an API-connected frontend.
ExplorePRODUCT & ENGINEERINGUse workspace roles, scoped keys and delivery logs. Add eligible approval and collaboration features as your needs grow.
ExploreCONTENT TEAMSPrepare copy, sections, translations and SEO fields from inside the CMS. AI requires configured services and available allowances.
ExploreCREATORS & OPERATORSPRICING
Block editor, REST + GraphQL API, 10 languages, community support.
within plan limits
Start freeIncludes
FOR CONTENT TEAMS
CMS and API only: no renderer or hosting included, bring your own frontend.
Billed monthly €90.00 · Billed yearly
Get started14-day free trial
Includes
Adds cookie consent, five webhooks, a 90-day audit log and email support.
Billed monthly €190.00 · Billed yearly
Get started14-day free trial
Includes
Hosting add-on
Provisioned on Altovar Cloud. Requires an Osprey base plan.
Your infrastructure
Run Osprey on your own servers with the self-host stack and the first-run setup wizard.
A headless CMS by Altovar for structured content, visual page editing, media and localized publishing. Your frontend stays separate from the content workspace.
Yes. Work with blocks and a connected frontend preview. The visual editor requires the frontend integration and preview bridge to be configured. Try the local interactive editor on this site.
Configure up to ten content locales per workspace, edit localized fields and inspect translation coverage. The admin interface has five languages. AI translation depends on service configuration and allowance.
Help prepare draft pages, sections, copy, translations and SEO fields inside the CMS. It requires configured AI services and an available allowance. Actions follow the signed-in user’s permissions.
Limits and included features come from the billing catalog. Advanced approvals, live collaboration and field permissions require an eligible plan or contract; they are not implied by Starter.
Yes. Osprey has first-party Astro and React/Next.js support, REST APIs and read-only GraphQL. Managed hosting and self-hosting are available; private packages and deployment access follow your agreement.
One workspace. From the first draft to your frontend.