You own it
Your organisation’s knowledge remains yours. Ownership is the foundation.
Your knowledge belongs to you. We help you capture, organise and use it, with the freedom to take it with you.
Your organisation’s knowledge remains yours. Ownership is the foundation.
Readable formats make your memory useful beyond one platform.
Preserve provenance and metadata, so you can understand your knowledge.
Define access and deployment around your organisation’s needs.
Keep a shared foundation of organisational memory independent of your AI tools. Bring the context you need into the places where work happens.
Your AI tools
Your sources. Your permissions. Your choice of AI.
Connections are scoped to your deployment.
A useful export should let you understand your memory and rebuild it elsewhere. That takes more than a pile of unlabelled files.
Structured JSON or JSONL, with a documented schema and a human-readable guide.
Source references, timestamps, ownership and permission metadata. Original content where your rights and source permissions allow.
Know what’s included, what needs reconnecting and how to validate a migration. No proprietary format keeping you here.
The download is a fictional sample that demonstrates the proposed export structure. It contains no customer data.
The details of data handling belong in your deployment agreement. These are the questions we’ll work through together.
Define users, roles, source permissions and administrative responsibilities before connecting knowledge. Access should follow an agreed model across the memory layer and connected tools.
The answer depends on your selected tools and deployment. Agree which content may leave your environment, which providers may process it, and the applicable retention and model-training settings before activation.
The portability direction includes structured memory and its metadata, source references, ownership, permissions and a schema guide. Original files depend on source-system access and your rights to export them. Embeddings, if included, need model and version information and may require regeneration elsewhere.
Your deployment agreement should define export access, retention, deletion, backups and migration responsibilities. A clear exit process is part of making ownership meaningful.
This local edition uses no analytics, tracking cookies or remote forms. The demo planner creates a file on your device and does not transmit its contents. If a booking service is configured later, its privacy terms will apply when you visit it.
Choose where it lives. Choose where it goes.