What core.blue is
A house is a database your agent designs for itself. It decides what kinds of things there
are (a person, a letter, a parish-register entry), stores them with documents and their
versions, and every statement keeps where it came from. a-house-by-example shows one.
Technically, a house is a private installation of Atlantis, a content-addressed graph memory with self-describing semantics. The agent defines the forms, aspects and concepts its purpose needs, stores things, links, documents and open questions under them, and asks the house in full text, by meaning, by time, by place and by structure. A house runs on a dedicated virtual machine with its own address, or on the customer's own hardware. Nothing is shared between houses.
A house is not a chat memory. It does not keep snippets of conversations and replay them. It keeps a world model: individuals, values, facts that are retracted rather than deleted, documents with all their versions, time with its precision.
A house explains itself. An agent that has never seen it calls overview, which returns
what is in the house and a description of how to read it; list_skills and read_skill
describe every skill with its parameters; list_forms and list_concepts show the
vocabulary earlier agents built. Agents are replaced; the house stays.
Who it is for
Agents that act on behalf of a person or an organisation over a long time and need to
remember more than a context window holds: a research agent, an assistant that runs a
business, an archive agent, a project agent. Not a memory that follows one person from chat
to chat: compared-to-other-memories says when a house is the wrong choice.
Who works with it
A person works with a house through their agent. Any assistant that can add a remote MCP
server can be that agent, and several can use the same house one after another. There is no
app and no screen for people: the person sees what their agent reports. With the size
on-premise the machine is the customer's; the desktop programs the house software has on
Windows are not part of the offer.
How it is delivered
| Size | Where |
|---|---|
economy | a small dedicated VM |
premium | a larger dedicated VM |
on-premise | the customer's own machine, with an offline licence |
All sizes run the same kernel. See sizes-and-volumes for what differs.
Who does the thinking
Storing, linking, searching and querying are deterministic and need no language model.
Judging does: classifying a document, deciding that two names are one person, summarising.
In a house you do the judging, on the model you already run. No API key is needed. If a
house should also judge while no agent is visiting, a model can be attached to it; that is
planned and described in who-does-the-thinking.
Who operates it
Code Intelligence Labs operates core.blue. VM houses run in Hetzner data centres; you
choose the country. Every house is its own machine; moving one onto your own hardware is
planned (your-data-stays-yours).
What you can do right now
- Open a sandbox: a real house for three hours with one call of
open_sandbox, without an account (the-sandbox). - Read this manual and ask
pricingandrecommendwhether a house fits and what it would cost. - Put a person on the waiting list, where the desk keeps one (
requesting-a-house).
A house of your own on its own machine is not yet available, and there is no date.
what-does-not-exist-yet lists everything planned in one place; read it before you tell
anyone what core.blue can do. What this manual says about the inside of a house was
checked against a running house.
Go deeper
- A house by example: one small case, call by call
- A memory you can shape: defining your own vocabulary
- Who does the thinking: what works without a model
- Getting a house: the stages from first call to a running house
- What does not exist yet: the honest list