Viking CMS
Take control of your website.
Create visually. Write in Markdown. Publish a complete static site.
Bring your content to Viking CMS and give it a new home: a browser-based editor for your team, themes you can make your own, and a public website served independently of your CMS. Self-hosted on Kubernetes. Open source. Yours to run.
Move from WordPress · Launch your first site · Explore the editor
Build a site that feels like yours
Shape landing pages with drag-and-drop sections, columns, cards and hero blocks. Write articles in a familiar visual text editor, or switch to Markdown source. Preview desktop, tablet and mobile layouts before sharing your work.
| Make it happen | What Viking gives you |
|---|---|
| Write your way | Visual Markdown editing, source editing, tables, images, task lists and .md upload/download |
| Design without starting over | Visual HTML pages, reusable blocks, Layers, Styles and Properties controls |
| Give every page a shared identity | Bundled and custom themes, reusable headers and footers, page layouts, images and fonts |
| Help visitors find their way | Ordered menus, submenus, automatic page indexes and repeated cards |
| Share more than pages | A media library and downloadable files with their own descriptive pages |
| Extend your toolkit | Install local ZIP packages containing blocks, themes or additional content renderers |
Bring your WordPress content with you
Start with a WordPress XML export or a read-only MySQL/MariaDB connection. Inspect posts and pages, review destination URLs and conversion notes, and choose what to import. Viking creates editable Markdown drafts for you to refine, style and publish while your existing site stays available.
Copy supported public images into Viking's media library, choose a native theme, and review the result before switching your domain. You decide when to go live.
Follow the WordPress migration guide ?
Coming from another platform? Bring your Markdown files through the editor, or use automated content uploads for an existing content pipeline.
Publish with a clear moment of change
Save drafts privately. Preview your work. Publish the saved site as a complete release, including its pages, theme and assets. Viking prepares the new release before switching the public site to it. Configure release retention to give your team a rollback option for previously published output.
The public frontend serves static files from read-only storage. Visitor requests run independently of the editor, sign-in provider and editable content store. Your team can work on the next version while visitors browse the published one.
Explore publishing and rollback ?
Your platform. Your identity. Your content.
Run Viking on your Kubernetes infrastructure with separate public and CMS addresses. Connect your organisation's OAuth2/OIDC sign-in, choose who can edit and publish, and manage sites through Kubernetes Website resources. Scale public frontend replicas for each site and connect health checks, metrics and logs to your monitoring tools.
Viking CMS is Apache-2.0 licensed. Keep editable content on your own storage, export Markdown and theme bundles, and manage backups with your storage platform.
Already have access? Create and publish your first page ?
User and administrator documentation · Screenshot gallery · Contributor guide · Project backlog · Apache-2.0 license