Vellum Alternative
Migrate from Vellum to the open-source alternative
Moving off Vellum is mostly a decision about what a team needs to own. Bring the context and prompts you can, rebuild the shared governance, and run one job before you widen. Kortix is the open-source AI Operating System you land on.
From a personal assistant to a team platform, in four steps.
Real Kortix commands from the docs. Run them on your own machine or in Kortix Cloud.
Install
$ curl -fsSL https://kortix.com/install | bash$ kortix loginScaffold
$ kortix init my-company$ cd my-companyShip
$ kortix shipkortix.yaml
kortix_version: 2default_agent: support-triageenv: optional: [HELPDESK_TOKEN]agents: support-triage: file: agents/support-triage.md connectors: [read-ai] secrets: [HELPDESK_TOKEN]connectors: - slug: read-ai name: Read AI provider: mcp url: 'https://api.read.ai/mcp'triggers: - slug: daily-digest type: cron cron: "0 0 9 * * 1-5" prompt: Summarize yesterday's support tickets and open a change request.What carries over
The prompts and job notes you wrote for Vellum are text, so they move across by hand. In Kortix, an agent is agents/<name>.md (behavior) plus an agents.<name> block in kortix.yaml (governance), so the instructions you already trust become the agent's file. Context that lives in Vellum's memory has to be written down; Kortix keeps company memory as files in the project repo, so anything worth keeping becomes a file the team can read.
What you rebuild
Governance does not transfer, so you build it on purpose. Kortix sets each tool call to Allow, Ask or Block, keeps per-resource permissions for people and agents, and lands session work through a change request a person approves. Write those rules as kortix.yaml entries and connector policies, and give each agent only the reach its job needs.
What stays a personal tool
A personal assistant is still the right shape for one person's inbox, calendar and notes. Vellum fits that work, and its own page says it is open source and runs on your machine or in its cloud. Keep the personal assistant for personal work, and let the company system carry the jobs several people depend on.
Run one job first, then widen
Move one job to Kortix before the rest: a weekly digest, inbox triage, or a report. Start with kortix init and kortix ship, watch the first session, and merge its first change request. One job that lands cleanly teaches the team the review habit faster than a large migration plan.
Where the numbers land
Kortix and Vellum price two different shapes. Vellum's cloud plans run from $30 to $200 a month for one assistant. Kortix's team plan is $40 per seat per month with 2,500 credits per month per seat, pooled, and self-host is free. The Vellum pricing breakdown sets both side by side before you commit.
Migration questions
What moves, what you rebuild, and what you leave behind.
01Can I import my Vellum memory into Kortix?
Kortix keeps company memory as files in the project repo, so you carry context across by writing the facts you rely on into memory files the team can read. The agent files beside them hold the instructions for each job.
02How do I start the move?
Start with one job: install the CLI, scaffold a project, write one agent file, and ship. The rest of the team follows job by job, with each change reviewed before it lands.
03Do I keep my Vellum subscription?
That is your call. If you keep a personal assistant for personal work, keep the plan that fits it. Kortix covers the jobs a team depends on, and its pricing is per seat rather than per assistant.
04Do I have to move everything at once?
No. Run one job on Kortix first and leave the rest where it is. Nothing merges without a person reviewing the change request, so you can widen once the first job lands cleanly.
Start with one job on the open-source platform.
Install the CLI, scaffold a project, and ship.
Open source · Any model, your keys · Self-host, VPC, or on-prem