Cookies on Kythene

We use cookies and similar technologies for the things below. You can accept all, reject everything except what's essential, or pick what you're OK with.

Preferences
Theme, language, dismissals. Improves the experience but the site works without.
Improvement
Anonymous usage measurement so we can fix bugs and prioritise work.
Marketing
Lets us measure whether ads we run send people who actually use the site. We don't share personal data with advertisers.

Read our cookies policy and the privacy policy. California residents: Do Not Sell or Share My Personal Information.

Loading…

Self-hosting

Run Kythene inside your own boundary.

The same shared context layer, on your infrastructure. For teams whose work - and whose AI's work - can't leave the building.

Data-sovereign teams

Keep every artifact, memory and event on infrastructure you control.

Regulated work

Permissioned tags and an activity log, inside your compliance boundary. On Enterprise we support your HIPAA, SOC 2 or ISO 27001 programme with security documentation and a BAA on request.

Air-gapped environments

An offline licence means no phone-home and no dependency on our servers.

The licence

Offline by design.

A self-hosted Kythene runs against a signed, offline licence. Your instance validates it locally at startup - it never calls home, and it keeps running whether or not it can reach the internet.

When it's time to renew, you drop in a new licence. That's the whole mechanism: no metering service to depend on, nothing that can quietly switch your team off.

on your servers
at startup
licence validate --offline
signature ok · plan team · valid
Kythene is up. No outbound call made.

Getting started

01

Deploy the image

Run the Kythene container against your own Postgres and object store. Free for a single user - the self-hosting guide walks you through it.

02

Set up in the browser

First run walks you through creating your admin and getting the team on. No config files to guess at.

03

Add a licence to grow

For your team, drop in a licence key (Enterprise self-host) to lift the cap and unlock paid features. It validates offline - no phone-home.

Your data is yours

No lock-in. We find the idea offensive.

Trapping your data to keep your business is not a strategy we will ever run. Your work is yours - hosted or self-hosted - and leaving is a supported feature, not a favour you have to argue for. If you ever want out, we hand you everything and hold the door.

That is not a slogan. It is why export, scheduled backups and a self-host option are in the product on day one, not a roadmap promise.

Export the lot, any time

Export a whole workspace to a readable tree - artifacts, memory and metadata - in formats you can open without us. Reachable even from an archived workspace, so a way out is never blocked.

Scheduled backups

Set recurring backups with a retention window, so you always hold a current copy of everything - not just a promise that we do.

Open formats, and the door out

Markdown stays markdown; files stay files. And you can take the whole thing in-house and run it yourself under an offline licence, whenever you like.

Bring it inside.

Free for a single user. Need it for your team (Enterprise self-host)? Request a licence and we'll get you set up.