Osprey

THE PLATFORM

Every part of your content operation.

A connected workflow for content models, pages, languages, AI and delivery. Explore the capabilities behind each stage.

The Blog Post collection in the admin: three documents with title, slug and a coverage chip for each of the ten locales, EN and IT filled in.The Blog Post collection in the admin: three documents with title, slug and a coverage chip for each of the ten locales, EN and IT filled in.

OSPREY01

Model your content

What you write on the left is what editors get on the right.

Explore
The Osprey admin editing a published page in place: the live page in the middle with fourteen editable fields outlined, the field list on the left, the locale selector and the Publish button in the toolbar.The Osprey admin editing a published page in place: the live page in the middle with fourteen editable fields outlined, the field list on the left, the locale selector and the Publish button in the toolbar.

OSPREY02

Build and edit visually

Give every page, collection and language a place to grow.

Explore
The workspace translations page: ten locale cards with coverage bars, EN and IT at 100 percent, and a per-page matrix below.The workspace translations page: ten locale cards with coverage bars, EN and IT at 100 percent, and a per-page matrix below.

OSPREY03

Work across languages

Every localized field, every locale, counted.

Explore

OSPREY04

Create with Altovar AI

Altovar AI works inside the CMS: plan a site, prepare draft pages, improve text, generate sections and help fill translation or SEO gaps.

Explore
The pages list in the admin: Home, Contact, Features and Pricing, each with its status, its slug and a ten-dot translation coverage.The pages list in the admin: Home, Contact, Features and Pricing, each with its status, its slug and a ten-dot translation coverage.

OSPREY05

Review, then publish

Drafts stay private. When you publish, the entry becomes available to the connected site, and a signed webhook can trigger a rebuild.

Explore

OSPREY06

Connect your frontend

Keep your frontend and connect it through REST, read-only GraphQL, the TypeScript client or the Astro loader.

Explore
The webhooks settings: one endpoint named Rebuild the site, active, subscribed to document and page publish events.The webhooks settings: one endpoint named Rebuild the site, active, subscribed to document and page publish events.

OSPREY07

Run your content operations

Media, SEO, forms and webhooks connect content to the work around it.

Explore
The API keys settings: one key labelled Default, its preview reduced to the last four characters, with the read-only flag and the creation date.The API keys settings: one key labelled Default, its preview reduced to the last four characters, with the read-only flag and the creation date.

OSPREY08

Keep control of access

Give people the access they need. Keep a history of changes and a path back to earlier content.

Explore

OSPREY09

Build on your terms

A typed client, an Astro loader, a CLI, an MCP server and a self-host stack.

Explore

Model your content

What you write on the left is what editors get on the right.

14 · CODE-FIRST FIELD TYPES
Text, textarea, rich text, number, boolean, datetime, slug, select, relation, media, group, array, JSON, blocks. All exported by the core package.
Flags, not screens
required and localized are two booleans on the field.
Also from the admin
Custom collections can be created in the admin and stored in the database.
The Blog Post collection in the admin: three documents with title, slug and a coverage chip for each of the ten locales, EN and IT filled in.The Blog Post collection in the admin: three documents with title, slug and a coverage chip for each of the ten locales, EN and IT filled in.

Build and edit visually

Give every page, collection and language a place to grow.

Visual editor
Pages, articles, collections and media. Define your fields in TypeScript or create a collection from the admin, then edit content in the workspace.
Collections
Required fields, the locale selector, the rich-text body. Nothing is configured twice.
The Osprey admin editing a published page in place: the live page in the middle with fourteen editable fields outlined, the field list on the left, the locale selector and the Publish button in the toolbar.The Osprey admin editing a published page in place: the live page in the middle with fourteen editable fields outlined, the field list on the left, the locale selector and the Publish button in the toolbar.

Work across languages

Every localized field, every locale, counted.

Content locales
en, it, es, de, fr, nl, pl, sv, pt, ro.
Admin
English, Italian, German, French and Spanish, switched from the top bar.
Coverage
A matrix per page and locale, and the missing strings as a CSV.
Delivery
One query parameter picks the language; hreflang alternates travel with each entry.
The workspace translations page: ten locale cards with coverage bars, EN and IT at 100 percent, and a per-page matrix below.The workspace translations page: ten locale cards with coverage bars, EN and IT at 100 percent, and a per-page matrix below.

Create with Altovar AI

Altovar AI works inside the CMS: plan a site, prepare draft pages, improve text, generate sections and help fill translation or SEO gaps.

A conversation with your content
Read pages and collections, plan a sitemap and build draft pages with the integrated agent. Available actions follow the signed-in user’s permissions.
Help at the point of creation
Improve copy, generate page sections, propose SEO fields and alt text, and translate missing strings from the editor.
Activation and allowances
AI requires a configured service and an available workspace allowance. Background helpers are opt-in; availability depends on configuration and plan.

AI requires a configured service and an available workspace allowance. Background helpers are opt-in; availability depends on configuration and plan.

Review, then publish

Drafts stay private. When you publish, the entry becomes available to the connected site, and a signed webhook can trigger a rebuild.

Review
Check the preview, review changes and keep a version history. Advanced approval and scheduling follow eligible plans and configured workers.
Revisions
page history with diff and restore
Trash
deleted pages wait; restore them or delete for good

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.

The pages list in the admin: Home, Contact, Features and Pricing, each with its status, its slug and a ten-dot translation coverage.The pages list in the admin: Home, Contact, Features and Pricing, each with its status, its slug and a ten-dot translation coverage.

Connect your frontend

Keep your frontend and connect it through REST, read-only GraphQL, the TypeScript client or the Astro loader.

REST
Public entries need no key. Back-office documents need an API key or a bearer token.
TypeScript SDK
A typed client with the same envelope: data and pagination.
GraphQL
Queries only, over POST.
Astro loader
Entries land in Astro content collections at build time. No key on the edge.

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.

Run your content operations

Media, SEO, forms and webhooks connect content to the work around it.

Media library
Upload and organize assets, manage alt text, and serve image transformations through the media API.
SEO and delivery metadata
Manage page titles, descriptions, canonical URLs and language alternates alongside the content.
Forms and newsletters
Collect form submissions and manage newsletter subscriptions through the CMS, with workspace settings and admin tools.
Signed webhooks
Connect publishing events to a build or external workflow. Inspect deliveries and request redelivery from the webhook tools.
Custom domains
Manage domains and prove ownership through DNS verification. Availability follows the hosting and plan configuration.
Commerce and content extensions
Product, order and coupon collections extend the CMS. Additional content plugins are loaded through deployment configuration.
The webhooks settings: one endpoint named Rebuild the site, active, subscribed to document and page publish events.The webhooks settings: one endpoint named Rebuild the site, active, subscribed to document and page publish events.

Keep control of access

Give people the access they need. Keep a history of changes and a path back to earlier content.

Roles
admin, editor, author, contributor, viewer
API keys
Five workspace roles and scoped, expiring API keys keep access explicit. Advanced permissions follow plan eligibility.
Audit log
who, what, when and from where, for users, API keys, webhooks, domains, collections and media
Rate limits
one bucket per route family, limits in the response headers

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.

The API keys settings: one key labelled Default, its preview reduced to the last four characters, with the read-only flag and the creation date.The API keys settings: one key labelled Default, its preview reduced to the last four characters, with the read-only flag and the creation date.

Build on your terms

A typed client, an Astro loader, a CLI, an MCP server and a self-host stack.

@osprey/client
typed SDK, React block renderer, consent manager
@osprey/astro
content loader, SEO head, translations sync
CLI
setup, init, dev, build, generate-types, link, export

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.

Create content. Keep control.

Explore the editor