The AI command center
for your company
Build internal agents like software. Define their skills, tools, persona, and guardrails as code, then deploy them wherever your team works.
The coding-agent loop, for real work
Describe intent, an agent edits files, you review the diff. Alqemist runs that same loop for support, ops, and research.
Agents are sandboxes
Every agent runs in its own disposable cloud VM, on its own git branch. Spin up thousands in parallel — nothing is shared between runs.
Work is code
Agents, skills, triggers, connectors and policies are plain files in one repo. Diff them, review them in a change request, roll them back.
You own the stack
Open and source-available. Self-host the exact same stack, bring your own runtime and model keys. No black box, no lock-in.
From curl to production
One repo, one config, one command. The whole path, top to bottom.
Install & scaffold
One line installs the CLI. alqemist init scaffolds alqemist.toml and .alqemist/, wired to your coding agent.
Build it locally, like code
An agent is markdown — a persona, its model, and its tools. Skills are folders it loads on demand. Edit them by hand, or describe what you want and let your coding agent write them.
---
description: Acme's support agent. Resolves tickets end to end.
mode: primary
model: anthropic/claude-opus-4-8
tools:
lookup_order: true
---
You are Acme's support agent. Resolve customer tickets
end to end, with full product and order context.
Issue refunds under $500 on your own. Anything higher
goes to a human for approval.Declare the project in one manifest
alqemist.toml holds secrets, sandbox images, triggers, connectors, and channels. Versioned from the first commit.
kortix_version = 1
[project]
name = "acme"
# the OpenCode runtime config dir
[opencode]
config_dir = ".alqemist/opencode"
# a trigger runs itself, on a schedule
[[triggers]]
slug = "daily-digest"
type = "cron"
agent = "research"
cron = "0 0 9 * * 1-5"
prompt = "Summarize yesterday across Slack & Linear"
# connect a tool's API as agent tools
[[connectors]]
slug = "stripe"
provider = "http"
base_url = "https://api.stripe.com"
# answer where your team works
[[channels]]
platform = "slack"
agent = "support"Ship it
alqemist ship commits, pushes, builds the sandbox, and prompts for missing secrets. Triggers and channels go live immediately — no separate infra to stand up.
It runs as a fleet of sandboxes
Every session is its own VM on its own branch, booting the runtime and your repo. Spawn thousands in parallel — zero interference. A change request is the only way work reaches main, so everything is reviewable and reversible.
Bring your own runtime & model
Sessions run on an open runtime. Bring your own keys — Anthropic, OpenAI, local — or use Alqemist compute. Nothing about the runtime is hidden.
The whole lifecycle, one CLI
Scaffold, ship, run, automate, connect and review — one CLI does it all. The same binary is pre-authenticated inside every sandbox, so agents drive Alqemist with the exact commands you do.
Scaffold & ship
$ alqemist initScaffold alqemist.toml + .alqemist/
$ alqemist shipCommit, push, link & go live
$ alqemist validateType-check your manifest
Run & talk
$ alqemist sessionsSpawn & manage sandbox sessions
$ alqemist chatTalk to a session's agent
$ alqemist filesBrowse the repo, diffs & branches
Automate
$ kortix triggersCron & webhook automations
$ kortix channelsConnect Slack & chat surfaces
Connect
$ kortix connectorsWire up 3,000+ tools
$ kortix secretsManage encrypted secrets
$ kortix envPull / push as dotenv
Review
$ alqemist crOpen, review & merge change requests
$ alqemist accessInvite, grant & revoke access
Operate
$ kortix self-hostRun your own Alqemist cloud
$ kortix hosts useSwitch cloud ↔ local
$ kortix providersBring your own model keys