What happens if InkCMS goes away.

Every CMS evaluation eventually arrives at the same question, even if it's never asked out loud: what happens to my site if the vendor disappears? It's a fair question. We've watched it happen — to startup CMS vendors that shipped great products and went under, to enterprise vendors that pivoted away from their customers, to open-source projects that lost their maintainer.

We designed InkCMS with that question in mind from the start. Here's what survives each failure mode — and what we deliberately did not promise.

Every page on your site is a Markdown file in content/production/. Every menu is a YAML file in content/menus/. Every uploaded image lives in content/media/ with a paired Markdown sidecar describing it. Every snapshot, every history version, every audit log entry — files, on disk, in your filesystem.

If InkCMS the company vanished tomorrow:

• You could tar your content/ directory and serve the result from any static-site generator with light template work — Hugo, Eleventy, Jekyll, Astro all read Markdown with YAML frontmatter natively.
• You could keep using the running installer indefinitely. The license-validation server going dark does not stop your site from running. See "The heartbeat fails open" below.
• You could open the source we shipped you and fork it. You have full read access to every .cs file, every Razor view, every CSS rule. The wider .NET community can pick it up.

There is no database to extract from. No proprietary content format to reverse-engineer. No vendor-controlled API to lose access to. The data model is the filesystem.

Every InkCMS install validates itself periodically against https://inkcms.ai/validation/heartbeat. The heartbeat checks subscription status, refreshes the license blob on disk, and reports usage telemetry (page count, version, host) back to us.

Here's what happens when the heartbeat fails — meaning the server is unreachable, our domain has lapsed, or the company no longer exists:

• The install continues to operate. Every gated feature (admin authoring, AI assistant, snapshots, downloads) opens up. We call this "fail-open mode" and it's intentional. The code path is in InkCMS.Licensing/LicenseGuard.cs if you'd like to audit it directly.
• Page-limit enforcement releases. Soft buffers and hard blocks evaporate.
• Existing blobs stay valid. Your most recent successful heartbeat seeded a signed license blob on disk; that blob carries the keys your editor needs (including the Froala wildcard key) to keep working long after the server is gone.

This is not a marketing posture. It is an architectural decision baked into the runtime. If InkCMS.ai ever stops resolving in DNS, every install we've ever shipped continues running, unrestricted, indefinitely. The "kill-switch" reading of the heartbeat model is exactly backwards: the heartbeat is what we use to grant capability, never to revoke it.

InkCMS is source-available under a commercial subscription license. You can read, audit, and modify every line of code we ship. You can run the result on your own infrastructure with no third-party dependency at runtime.

You can't redistribute the source today — that's the line between "source-available" and "open source," and it's the line that lets us sustain the product as a business. But the source on your disk is yours, and if we ever closed shop or stopped maintaining the project, that source becomes the basis for community inheritance. There's nothing structural preventing a customer or a third party from forking and maintaining InkCMS after we're gone. The architecture is open enough to make that practical.

Honest scope:

• No third-party source escrow. We considered it. We didn't add it. Filesystem portability plus the source you already have makes escrow unnecessary in our view.
• No automatic open-source conversion clause. Some commercial-license platforms include a "this license converts to open-source after N years" trigger. We didn't take that path because central rotation of the editor wildcard key requires operator continuity. If we ever change that architecture, we'd revisit.
• No legacy customer support if we cease operations. Obviously. The point is that you wouldn't need us in that scenario — the installs keep running, your content is portable, and the source is yours.

If you're evaluating InkCMS and the continuity question is weighing on you, do this experiment with the free download:

1. Spin up an InkCMS install on localhost. (Localhost is unlimited, unactivated, always free.)
2. Add some content.
3. Block inkcms.ai in your hosts file. (127.0.0.1 inkcms.ai sends every heartbeat into a dead end.)
4. Restart the app. Use the admin. Edit a page. Run the AI assistant. Take a snapshot.

Everything still works. That's the design.