Skip to content
Open-source public betaMIT licensed

Where your team'swork comes together.

  • MIT licensed
  • Self-hostable
  • Claude & Codex via MCP

How work moves

One issue, from sketch to shipped.

Idea, Todo, and In progress are the columns every new project starts with. Rename them or add your own. Here's what happens to an issue on its way through.

  1. Idea

    Start with a rough sketch.

    Talk it through on a call and sketch it on the shared canvas. When it's worth doing, create an issue and attach the drawing. A chat message can become an issue the same way.

  2. Todo

    Give it an owner and a date.

    Set the priority, assignee, and due date. The issue lands in their Inbox and on the calendar, with comments and mentions in one thread.

  3. In progress

    Build it in GitHub.

    Create the linked GitHub issue from Origin, then work in the repository with your own tools. A branch icon marks the link on the card.

  4. Completed

    Close it once.

    Close the GitHub issue and Origin completes its counterpart. Finished work leaves the board but stays one click away, grouped by the column it finished in.

Around the work

Everything else your team reaches for.

No second app for calls, no third for secrets. The rest of the workspace sits one click from the board.

An inbox that's yours.

Assigned issues, mentions, and comments in one list. Switch to the week or month calendar to see what's due, and snooze what can wait.

Calls that stay open.

Audio, video, and screen sharing with your own TURN relay. Switch to Draw without hanging up.

A vault for shared secrets.

Keep credentials with the project. Values are encrypted in your browser with the vault passphrase before they're saved.

Feedback from outside.

Open a public form for any project. Triage what comes in privately, then turn the good ideas into assigned issues.

Finished work, out of the way.

Completed issues leave the board, not the project. They're grouped by the column they finished in, ready to restore.

Open source

Run your own Origin.

MIT licensed and self-hosted: run the Node server on your own machine with a Convex deployment. There is no shared hosted service, so your workspace stays on infrastructure you control.

Run it locally
$git clone https://github.com/z4mbo/origin-workspace.git
$cd origin-workspace
$npm ci --legacy-peer-deps
$cp .env.example .env.local
$npx convex dev
$npm run dev  # second terminal

Node.js 24+ and a Convex deployment. No OpenAI or Anthropic key required. Open localhost:3000/signup to create the first workspace.

What runs where
BrowserYour team, on any device
ConvexBoard, drawings, feedback, accounts, project assets
Node serverNext.js with SQLite for chat, calls, and integrations. GitHub OAuth, webhooks, and MCP.
coturnOptional TURN relay for call media
  • Next.js
  • React
  • TypeScript
  • Convex
  • SQLite
  • WebRTC
  • Excalidraw
  • Yjs

FAQ

Questions, answered.

Who can see my workspace?

Only its members. Each workspace is private. A public feedback form shows only the title and description an admin chooses, never internal issues or submitted feedback.

Do I need GitHub?

No. Issues, chat, calls, and drawing work on their own. Connect GitHub when you want linked issues and repositories. New repositories are private by default.

What can an AI client see?

Projects, issues, members, and your issue inbox in the one workspace you authorize. Not chat messages, the vault, GitHub credentials, or code execution. Grants expire, and you can revoke them.

Does it work on my phone?

Yes. Check issues, catch up on chat, and open the canvas from your mobile browser. Camera and screen sharing need HTTPS outside localhost.

What happens when an issue is done?

It moves to the project's Completed view, grouped by the column it finished in. It doesn't take up a column or count toward open issues, and you can restore it anytime.

Clone it. Host it. Invite your team.

your-origin.example/your-team