DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to run a self-hosted issue tracker on your own machine with Itsaplan

Start the full It's a Plan stack in Docker on localhost and try boards, cycles, and docs.

Who it is forA team lead or developer who wants to evaluate an open-source alternative to Linear or Jira without a SaaS account.

The problemHosted trackers charge per seat and lock data in a vendor's cloud, which makes trying a new tool costly and slow.

The outcomeA running instance on localhost with kanban, table, timeline, and calendar views, ready for a first project.

What you need first

  • Docker and Bun for a local try-out, or a Railway account with a domain of your own for hosted deploy
  • A model or coding CLI for internal or external agents, if you use agents
  • Admin access to the instance to set up agents and API keys

Steps

  1. Install Docker and Bun, then clone the repo with git clone https://github.com/croffasia/itsaplan.git.
  2. Change into the folder with cd itsaplan and install dependencies with bun install.
  3. Run bun run setup and answer "Try it" when asked.
  4. Open the address the setup prints, create an account, and create your first project.
  5. Run bun run setup again later to restart the instance. Your data stays.

Prompt for your agent

In the itsaplan repo at <path>, run `bun install` and `bun run setup`, answering "Try it". Report the local URL the setup prints and confirm that the Kanban, table, timeline, and calendar views load for a new project.

Caveat. The README says the project is under active development and expects breaking changes before the first stable release, so do not treat a try-out instance as production.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page