Projects and issues
Issue keys like PLT-12, a status workflow, priorities, estimates, sub-issues and blocking relations. Every issue is a page, with comments and a timeline.
What works today
Everything your team writes and plans, in one place.
Docs and issues share one model: everything is a page. Issues get the editor, comments and sharing, and docs can hold databases of anything.
Cycles
Sprints with a board that follows the running cycle, a burn-up chart, and unfinished work carried over when a cycle ends.
An editor worth writing in
Tables, code, callouts, columns, math and embeds, with autosave, version history and inline comments.
Databases
Tables, boards and lists with typed properties, two-way relations, and filters and sorts saved per view.
Agents over MCP
Claude, Cursor or your own agents search, read and update issues and pages as you, with a key or by signing in.
GitHub pull requests
Branches, commits and pull requests link to issues by key, pull requests list their issues, and merging one completes its issue.
- Keyboard-first: C, S, ⌘K
- Import from Jira, Linear or GitHub
- A REST API for your scripts
- Webhooks to Slack and anything else
- Inbox and email digest
- Full-text search
- Public share links
- Roles and invitations
- Sign in with GitHub or Google
- Trash with restore
- AI with any OpenAI-compatible model
Self-host
Three commands. Four containers. No other accounts.
The setup script writes your secrets, and Compose builds the app and starts it with a job worker, Postgres and file storage. Migrations run on start. Only the app's port is exposed.
- appThe web app, on one port
- workerEmail, digests and cycles
- PostgresEverything but files
- SeaweedFSUploads, or any S3 service
git clone https://github.com/ordenhq/orden.gitcd orden && npm run setupdocker compose up -d --wait# then open http://localhost:3000HTTPS, email, AI models, your own Postgres or S3, backups and upgrades are in the self-hosting guide.
Built to be run by you
A workspace you own, not one you rent.
Nothing else to sign up for
Postgres, S3-compatible storage and SMTP, all of which you can run yourself. The AI model is whatever OpenAI-compatible endpoint you point it at, including Ollama or vLLM, or none at all.
Everything is a page
A doc, a database row and an issue are the same thing underneath, so features land everywhere at once instead of in separate silos.
Private by default
Sign-up is by invitation unless you open it. Roles decide who edits, publishes and deletes, and pages you can't read don't exist as far as you can tell.
Yours to read and change
MIT licensed, with tests for the permission rules and browser tests of every main journey, run in CI on each change.
Next
Where it's going.
Orden is early. These are planned, in this order, and none of them ship yet.
- Planned
Your GitHub, your name
Connect your GitHub account, and pull requests and commits show up as yours, not as a GitHub login.
- Planned
Real-time editing
Several people typing in one page, with presence, live cursors and boards that update on their own.
- Planned
Agents as members
Assign an issue to an agent, read its plan in the comments, and approve the pull request it opens.
Your team's workspace, on your own server.
Clone it, start it, and invite your team. Your data stays in a Postgres database you can back up with the tools you already use.
docker compose up -d --wait