Half-configured templates are how pilots die: an agent pointed at a table that doesn't exist, a trigger that never fired, a failure nobody saw. This installer leaves no room for that. You read the full blueprint, answer a few setup questions, and a deterministic installer builds the department bottom-up in dependency order — ending in a smoke test, not a hope.
A complete department out of the box: tables, agents, triggers, and a named AI employee. Live in about fifteen minutes.
Browse packsA single agent, team, employee, or table, ready to install and edit. Grow it into your own system.
Browse templatesThe full platform underneath: your tools, your data, your models, your governance rules.
See the platformYou see the entire department before anything is created: every component the pack installs and every tool it needs connected.
A few plain-language choices configure the pack for your rules: which sources it watches, guardrails like a daily outbound email cap, and the approval gate. Setup asks the governance question before anything runs: for example, should the AI employee require human approval before sending external emails?
If a component with the same name already exists in your workspace, you decide what happens: use existing, rename, or replace. Nothing gets clobbered.
Components install bottom-up in dependency order, and a live log shows every step. The run ends with a final verification and smoke test.
A working department, not a project plan. Open your new coworker and assign the first task.
Components install bottom-up so nothing ever references a thing that doesn't exist yet: tables first, then knowledge bases, agents, triggers, and finally the AI employee. Bindings and @mention placeholders resolve automatically along the way — and the run doesn't end until the smoke test passes.
When a pack component collides with something you already built, the wizard stops and asks. Three options, all explicit.
Keep the component already in your workspace and wire the pack to it. Nothing is duplicated.
Install the pack's version alongside yours under a new name. Both stay.
Swap your component for the pack's version. You choose this explicitly; it never happens by default.
Don't build an AI team. Install one, and govern it like staff.
