Sizes and volumes
Three choices describe a house: the size, the volume, and whether a model is attached.
Size: the machine
economy | premium | on-premise | |
|---|---|---|---|
| Meant for | one person: a researcher, a writer | an organisation | material that must stay in your network |
| Where it runs | a small dedicated VM | a larger dedicated VM | your own hardware |
| Additional data volume | no | yes | your own disks |
| Kernel: graph, forms, aspects, documents, plans | yes | yes | yes |
| Full-text and semantic search | yes | yes | yes |
| All three doors | yes | yes | yes |
| Borrowed mode: you do the judging | yes | yes | yes |
| Local name finder (planned) | no | yes | depends on the machine |
| Local OCR (planned) | no | yes | depends on the machine |
economy is deliberately kept free of additional compute-heavy work, so that a small
machine stays responsive. What premium adds is local computation that needs a bigger
machine and no language model: a name finder that marks person, place and organisation
names in text, and OCR that makes scanned documents searchable. Both are planned and not
yet built.
All sizes run the same software. Nothing in economy is a reduced version of the kernel;
semantic search, for instance, runs on every size.
Measured on the current version: an empty house occupies about 0.7 GB of memory and starts in about two seconds. Houses with a few hundred megabytes of data occupied between one and two and a half gigabytes. These are observations on a development machine, not guarantees.
Volume: how much it holds
An economy house holds what the disk of its machine holds; how much that is, is not yet
decided. Only a premium house can have additional data volumes attached, within bounds
that pricing names. Material that outgrows economy is the first reason to move to
premium; moving keeps the house. An on-premise house is limited by your own hardware;
its licence does not limit the amount of data.
Model supply: whether the house can judge by itself
Not a property of the size. Every size runs without a model; attaching one is planned as a
separate choice. See who-does-the-thinking.
Which size to ask for
- Start with
economyif you are one person and your material is text you already have as text: notes, Markdown, web pages, structured records. Everything described in this manual under "Inside a house" works there. - Choose
premiumif you are an organisation, if your material is larger than a small machine holds, or if you will depend on the planned local name finding or on scanned documents once OCR exists. - Choose
on-premisewhere the material must not leave a network you control. The software is the same; you operate the machine, and the licence is a file the house verifies without contacting anyone.
Moving between sizes is planned to keep the house: same address, same content, a different machine.
Where the machines are
VM houses run in Hetzner data centres, and you choose the country among those Hetzner offers. core.blue is operated by Code Intelligence Labs.
Prices
Call pricing. It returns the offer as data: the price of each size per month, the
one-off price of the 14-day test, the price of additional volume per gigabyte, and what is
never charged. This manual states no amounts, so that it cannot contradict them. The
shape: a price per house that follows its size; additional volume at the supplier's price
plus a service fee; nothing per user, per agent or per call. The price of on-premise is
not yet decided.