Command line
Your job board is a codebase you own.
Pull the source, edit it in your own editor or hand it to an AI agent, run it locally against your live data, and deploy when it looks right.
Open source, Apache-2.0 · github.com/Kardow/kardow-cli
From nothing to deployed, in five commands.
No config file to write. pull leaves a folder that runs.
npm install -g kardow Node 18 or newer kardow login authorize this machine kardow pull acme-jobs download your board source kardow dev run it locally against live data kardow deploy build and publish What it does that a deploy tool cannot.
Other platforms hand you a build step. This hands you the whole tenant.
A whole board in one command
kardow orgs create makes the organization, claims the subdomain, deploys a live site, creates the source repo, and pulls it locally. Not a deploy: a tenant.
Preview, then promote
Every site version has its own URL. Deploy to it, look at it, then point your live domain at it with kardow template set.
Clone a board for a new client
kardow orgs copy takes an existing board’s design and binds it to a new organization’s data. The copy is a fork you own and can diverge freely.
Built for agents, not just people
Claude Code, Cursor and Codex drive these commands directly. Set KARDOW_TOKEN and it runs headless in CI or a cloud agent with no browser.
Every command.
Anything the dashboard can do to a board, the CLI can do too.
kardow pull <board> Download a board’s source kardow dev Run locally against live data kardow deploy Ship changed files to the live board kardow orgs create Org, subdomain, live site and repo kardow template set Switch which site is live kardow rollback --to <sha> Revert the source to a commit kardow config set Colors, languages, navigation kardow secrets set Vault-backed org secrets kardow status What this board is running kardow logs Build log from the last deploy Prefer to work in chat?
The MCP connector lets ChatGPT and Claude post jobs, publish pages and pull analytics without touching the source. Most people use both: chat for content, the CLI for the site itself.