Content model
Structured fields
Define the allowed type and validation for every field.
Connect the frontend you already built. Choose exactly what each client can change, and every edit stays a draft until you publish it.
Your first live site is free. No card required.
This is Halden, a demo product site. Change a changelog entry on the left; the published site updates on the right. Nothing goes live until you publish, and any version is one click back.
Changelog
Timelines now render in under 100ms, even for month-long incidents.
A cleaner public status page with per-region uptime and a subscribe button.
Failed webhook deliveries now retry with backoff for up to 24 hours.
Left: what the client edits in Veldon Edit. Right: the developer's own Halden frontend, rendering published content. The same idea powers the hands-on demo at try.veldon.pro.
Set field types, validation and permissions once. The editor, API and assistants follow the same rules.
Content model
Define the allowed type and validation for every field.
Permissions
Editors and connected tools can perform only the operations you assign.
Versions
Every published version keeps the media it references.
Editor / assistant → content model → permissions and validation → versions → delivery API → your frontend
Why it works
Your frontend fetches published content through the HTTP API. Compatible assistants use MCP to perform only the operations you allow.
Frontend control
Keep your framework and frontend code. Veldon Edit adds structured content, publishing and rollback.
Client separation
Manage client sites in one place, with separate permissions for every client.
Product extension
Add content management through the API while keeping your own admin.
Start with one live site, one user and no card.
Free
€0
Site
€19a month
Studio
€79a month
Agency
€239a month
Activate a paid plan from your dashboard after signup.
No. Keep the site as it is, whether it was hand-built, made in Framer, or generated with AI. Wiring it up means fetching the published JSON and placing the values into your templates.
No. Clients edit only the fields you expose, and each field has a type and rules. The code and design stay with you, and any published version can be rolled back.
Only the operations you allow, under the same data rules as any human editor. Edits land in a draft and reach the live site only when published.
Your website keeps running, because it runs on your hosting. An outage delays content edits and publishing, not your visitors.
No. Your content is the same plain JSON your site already reads, and media live on stable URLs. Download the latest version any time and walk away.
There is none. One live site, one user, and limits an ordinary site won't hit. You pay once you need more sites, users, or content.