Whitepaper · Platform choice
The vendor lock-in you always wish you had
Every AI platform locks you into something. That is a trade-off, and you can choose it. This paper sets out what you trade, how Curiosity handles each part, and how to test any vendor’s exit before you sign. Written for the people who choose.
What it covers
Lock-in is a trade-off. Choose it on purpose.
Any useful system collects your work: joined records, rules for who sees what, tools people rely on. Whichever platform you pick, you accept a trade-off. With Curiosity, what builds up lives in your own context, on your own servers, in files you can read.
- Layer 01
Model
Prompts, tuning, habits
- Layer 02
Data
Records and their links
- Layer 03
Permissions
Who may see what
- Layer 04
Logic
Schemas, tools, agents
- Layer 05
Runtime
Servers, keys, operations
Chapters
Six chapters, from the problem to the exit
01 · Page 03All five layers
Every platform locks you in
The problem for any platform: waiting and building it yourself are lock-in too.
02 · Page 07Model
Curiosity lets you swap the AI model
How Curiosity does it: the model is a setting, not a contract.
03 · Page 09Data · Permissions
Curiosity lets you take your data out
How Curiosity does it: readable export first, then nothing migrated in.
04 · Page 13Logic · Runtime
Curiosity keeps what you build in your git
How Curiosity does it: schemas, endpoints and agents as files you hold.
05 · Page 15All five layers
What you are still locked into with Curiosity
How Curiosity does it: the cost of leaving is the value you built.
06 · Page 17All five layers
Six questions to ask any vendor
The questions apply to any vendor, and we answer them for Curiosity.
Your data. Your infrastructure.