Introduction
What Loomis is, and where to start reading.
Loomis is an AI workspace somebody runs themselves. Describe what you want, watch it get written into a real project, publish it at an address of your own. Around that sits everything a product needs to be a business: accounts, plans, credits, payments, teams, a marketing site, the legal pages, and a panel where all of it is configured without touching code.
This manual is for the person who bought it. It assumes you can read a screen and follow a link, and never that you write software.
Start here
A workspace
Chat that reads and writes files in a real project, with diffs you accept or refuse.
A published address
Projects can be deployed and served at a domain or subdomain you control.
An accounts system
Email and password, optional Google and GitHub sign in, confirmation, reset, sessions, audit.
A panel
Eight groups of settings that decide how every one of those behaves.
A marketing site
Landing page, pricing, resources and legal pages, all editable from the panel.
An installer
Two ways in: one double-click, or a terminal walk through the same questions.
For agents
The addresses a machine reads, and the prompt that turns a page into instructions.
What arrives
A folder named sourcecode: every file this product is built from, and no node_modules, because the
packages are downloaded rather than shipped. Beside it comes a quickstart PDF, which is the short form of
this manual: one machine, one installation, ten minutes.
The manual you are reading is part of what you bought
It lives in content/docs and it is served by the installation itself at
/docs. So once this is on a server, the documentation is online on your own
domain, under your own name, with no dependency on anybody else's website.
Edit a page and it is your page.
What it can answer with
One gateway key reaches all of these, which is why the list is companies rather than integrations to build.
Anthropic
OpenAI
Google
xAI
DeepSeek
Mistral
Moonshot
Perplexity
Alibaba
Kling AIWhich of them are live is a setting, not code: Intelligence → Models,
Model keys.
The four things a buyer actually does
- Install it. Double-click one file, or run one command. Both ask the same nineteen questions, and both can be finished later.
- Claim it. Create the first administrator, sign in, and change that password.
- Decide how it looks and what it costs. The name, the marks, the colours, the landing page, the plans, the prices.
- Put it on a server, where it lives at your address with your own database and your own keys.
Those four are the shape of this manual: Getting started, Configuration, The panel, The product, and Keeping it running at the end.
How to read a page
Pages that change something in the panel name the section and the screen exactly as they appear in the
sidebar, so Money → Plans & pricing is a place you can walk to. Commands are shown in full, with the
folder they are meant to be run in.
Two environments, and this is the part people get wrong
Half of the settings are read by the app, which runs on Node, and half are read by the deployment, which is Convex. They are different computers with different environments. A value set in the wrong one looks set and does nothing. Every variable page in this manual says which of the two reads it.
What is deliberately not here
There is no repository link, no hosted dashboard of ours, and no account with us. This copy is yours: it does not call home, it does not report usage, and nothing in it stops working because a company somewhere else changed a policy. That also means this manual is the support. Keep it.
Three things to do before you tell anybody else about it
Change the first administrator's password. It was chosen to get you in, not to keep anybody out.
Set your own SETTINGS_SECRET and BETTER_AUTH_SECRET. They are the two keys that seal other people's
tokens and sign sessions. Rotating the second one signs everybody out.
Decide who may sign up, in System → Security. The shipped answer is friendly, and a public address may
want something stricter.