Your first day with your Kastel.
From signup to an AI that answers on your real files: create your hosted space, connect your AI keys, choose what your Kastel reads, turn on what runs on its own, then plug in your AI.
Create your space
Signing up takes your email address and a name for your workspace. You receive a confirmation link by email, valid for 30 minutes and single-use. The other form fields (company, sector, size) are optional and gate nothing.
Once in, you choose where your Kastel runs: hosted by Kastel, or hosted by you. This section documents the first path. Kastel hosting is an isolated instance, for your company and nobody else, operated in Europe.
You then pick your plan and register your card: the subscription starts immediately, with no commitment, and can be cancelled anytime from your console. There is no hosted free trial: Kastel’s trial path is the free self-host. Plans, prices and included seats are on the Pricing page.
Healthcare, finance, public sector, industry with sensitive IP: the paid plan that concerns you is Enterprise, on quote, with no online checkout. Write to us, we answer the same day.
After payment, your space starts building on its own and takes a few minutes. You can leave the page open: it takes you to the next step as soon as your space is ready. Have an account with an AI provider at hand: your Kastel will ask you for a key right after.
Connect your AI keys
Your Kastel works with your company’s own AI keys: you hold the account with the AI provider, and the provider bills you, never Kastel. This step is mandatory: without a key, your Kastel cannot build anything.
Anthropic, OpenAI, Mistral, DeepSeek or Kimi, each with its jurisdiction shown. Already have an enterprise cloud account? You can plug in your own Amazon Bedrock or Google Vertex account, in a European region.
If you set one, your Kastel stops calling the AI for reading and building once the month’s cap is reached. Two uses stay outside the cap: search, which spends nothing at your provider because your Kastel ships its own search model, and lesson compilation. Change the cap whenever you want.
It is sent directly to your space, where it is stored encrypted. It is never kept anywhere else. It is the only key you will be asked for: search is computed inside your Kastel.
Connecting your AI keys gives your Kastel what it needs to read and build: the AI provider bills you for that work. Giving an AI access is something else: it authorises an external AI (Claude, Cursor, ChatGPT...) to consult your Kastel. That second gesture is covered by the Connect your AI guide.
Choose what your Kastel reads
The principle that governs everything else: the AI only ever passes over what a human designated. Your Kastel is not a mirror of your tools, it is a chosen corpus. Each department head decides their own scope, and nothing launches without a quote. The first two steps below chain on their own right after your keys are connected.
The documents that describe your company: org chart, company deck, offer, master procedures... A checklist guides you; nothing blocks, it indicates, it never demands.
Your Kastel asks you about your organisation, building on what you dropped. Started on one computer, the interview resumes anywhere. At the end, you confirm your organisation map: you are the one who confirms, and that confirmation is recorded under your name.
Your departments are the ones you just confirmed on your organisation map. Open one, then its Sources tab: pick a connected source (Google Drive, Slack or Notion), your Kastel lists the folders and channels it holds without opening a single document and without spending anything, and you tick what matters.
The quote is always a range in euros, with what remains of your monthly cap if you set one. If the high end exceeds the cap, the page says so before offering the button: trim your selection, or raise your cap. At the end, a report details what was read, what was skipped, and what it cost. What has already been read and has not changed is never re-read nor paid twice - the quote itself stays cautious and does not deduct that saving.
What already runs on its own
There is nothing for you to turn on: the functions that keep your Kastel in shape run from delivery, on your AI keys. They are listed here because you are entitled to know what your Kastel does without being asked, and you can stop any of them at any time.
The reason is sovereignty, not saving: what matters is not whether a function starts, it is that you can see it and stop it. The six:
Every week, re-reads the pages that could contradict each other and flags real conflicts. Uses your AI keys. Runs by default.
Checks right away that new content contradicts nothing existing. Uses your AI keys. Runs by default.
Remembers who said what and with what certainty. Spends nothing, ever: it runs permanently and is not a setting. Reading the statements is launched separately, quote shown.
A mechanical, free check, with no AI call at all. Runs permanently and is not a setting.
Distils what your agents learned into reusable lessons. The function whose switch-off degrades your Kastel the most. Uses your AI keys, outside your monthly cap. Runs by default.
Re-measures the Context Score so the figure shown stays fresh. Paused today: it does not run and spends nothing.
Everything is driven from the “What runs on its own at your company” page (Settings, then “What runs on its own”): turn off, turn back on, and read the month’s estimated spend for the functions that are metered. Only the owner or an administrator can touch it, and every toggle is recorded in your audit trail.
Plug in your AI
Last gesture of the first day: give your AI access to your Kastel. Each person connects their own AIs, the authorisation carries their name, and can be cut at any time from “Your connected AIs” (an already-open connection can stay active for up to a quarter of an hour). The Connect your AI guide gives the ready-to-paste connection block for Claude, Cursor, ChatGPT and any MCP client.
Your Kastel is built, your keys are in place, your AI is plugged in. The next step is inviting your team: people, roles, and a governance that records who decides what. You decide what each AI is allowed to see.