Skip to content
Back to search

lalabase

Open-source project management for software agencies with client projects: tickets, time tracking, docs, meetings and an AI assistant on your own data. Self-hosted with Docker or cloud in Germany. AGPL-3.0.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/lalabase/lalabase with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/lalabase/lalabase'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/lalabase--lalabase/badge.svg)](/listings/lalabase--lalabase)

HTML

<a href="/listings/lalabase--lalabase"><img src="/api/listings/lalabase--lalabase/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

bin/setup                           # dependencies, create the DB, load the schema, seeds (incl. demo)
npm install && npm run copy:fonts   # Bootstrap Icons into public/fonts (once)

Running it in development: two processes

`Procfile.dev` has **no web server** (only the CSS watcher and Solid Queue), so start the server separately:

bin/dev                      # terminal 1: Tailwind watcher + Solid Queue
bin/rails server -b 0.0.0.0  # terminal 2: the application

Signing in during development: a freshly created development database contains a small demo (`db/seeds/demo.rb`): `anna@example.com` (admin), `ben@example.com` (standard role), `clara@example.com` (project manager) and `david@example.com` (viewer), and `/admin` with `admin@example.com`, each with the password `lalabase-demo`. On an existing database, `bin/rails db:seed` creates them, and `bin/rails db:reset` rebuilds everything.

A fresh instance gets its first admin with `bin/rails lalabase:setup`.

Your own keys for every installation

The repository ships no encrypted Rails credentials. In development and test, Rails creates its own key in `tmp/local_secret.txt` on first start, and the local data encryption keys are derived from it. Keep that file for later starts. This is also why `.env.example` has no active `SECRET_KEY_BASE` example value.

For a **new** production installation, copy `.env.production.example` to `.env`, fill in the database and the mail provider, and generate your own keys:

bin/rails secret               # put the output into .env as SECRET_KEY_BASE
bin/rails db:encryption:init   # copy the three values into ACTIVE_RECORD_ENCRYPTION_*
bin/rails db:prepare
bin/rails lalabase:setup

With these environment variables, neither a credentials file nor a `RAILS_MASTER_KEY` is needed. If you use Rails credentials instead, create them yourself with `bin/rails credentials:edit --environment production` and put the matching key on the server. If `secret_key_base` lives in the credentials, remove or comment out the `SECRET_KEY_BASE` line in `.env`: even an empty environment value overrides the credentials. The three data encryption keys must still be set, in the credentials or in the environment. Credentials files and keys stay outside this public repository.

**Existing installations:** keep your existing credentials, master keys, `SECRET_KEY_BASE` and data encryption keys, and back them up separately from the source code. Existing credentials must still be provided through your deployment configuration after updates. New keys do not migrate existing encrypted data.

Running it with Docker

The Docker steps are [above](#self-host-with-docker). They install a release; for development, use the two processes described here.

Running an instance

The guide for that is **not in this repository**: [lalabase.com/docs](https://lalabase.com/docs) covers installation, operation, backups and updates, in German and English.

Until 21.09.2026 it lived as Markdown under `app/docs/`. This application **never** served it in production: the `/docs` routes were wrapped in `unless Rails.env.production?`, so they were only reachable in development, and the in-app help read from them. Since then the documentation is a program of its own (`gboyke/lalabase-documentation`), because it is not meant to fall under this repository's license. For a self-hosted instance that changes two things:

* `/docs` and `/hilfe` serve **no pages**. Instead of text, the in-app help shows links to the public documentation online. * If you want it inside your own instance anyway, put a catalogue file at `DOCS_CATALOGUE_PATH`. The format contract so far lives in the private documentation archive (`docs/api/katalog_v1.md`). The file is **generated** by the documentation program, which is not public, so for now it has to be written by hand.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 182 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <picture>
  3. <source media="(prefers-color-scheme: dark)" srcset=".github/readme/lala-assistant-dark.svg">
  4. <img src=".github/readme/lala-assistant-light.svg" width="760" alt="Lala, the Lalabase mascot, asks the assistant how many hours went into the shop relaunch in September. The answer: 38.5 hours across 12 tickets, most of it checkout and payment, with the tickets and the time list as sources.">
  5. </picture>
  6. </p>
  7. <h1 align="center">Lalabase</h1>
  8. <p align="center">
  9. <strong>A self-hosted project brain for devs and customers.</strong><br>
  10. <sub>RUBY ON RAILS · POSTGRESQL</sub>
  11. </p>
  12. <p align="center">
  13. <a href="https://github.com/lalabase/lalabase/releases/latest"><img src="https://img.shields.io/github/v/release/lalabase/lalabase?label=release" alt="Latest release"></a>
  14. <a href="LICENSE"><img src="https://img.shields.io/badge/license-AGPL--3.0--only-blue" alt="License: AGPL-3.0-only"></a>
  15. <a href="https://lalabase.com/docs/en/self-hosting/getting-started/overview"><img src="https://img.shields.io/badge/docs-lalabase.com-blue" alt="Documentation"></a>
  16. <a href="https://demo.lalabase.com"><img src="https://img.shields.io/badge/demo-live-brightgreen" alt="Live demo"></a>
  17. </p>
  18. Tickets, time tracking, docs and meetings for software agencies and their clients, with an AI
  19. assistant that answers from your own project data and cites its sources. Free on your own server,
  20. or hosted by us in Germany.
  21. **[Try the live demo](https://demo.lalabase.com)**: no sign-up, the login is on the page, and
  22. everything resets every night.
  23. [Website](https://lalabase.com/en) · [Self-hosting](https://lalabase.com/docs/en/self-hosting/getting-started/overview) ·
  24. [Cloud pricing](https://lalabase.com/en/pricing) · [Changelog](CHANGELOG.md)
  25. <table>
  26. <tr>
  27. <td width="50%" valign="top">
  28. <a href=".github/readme/ticket-assistant.png"><img src=".github/readme/gallery/ticket-assistant.png" width="400" alt="A ticket open in Lalabase with the assistant beside it. The ticket is the question's reference; the answer says who works on it and what is still open, and cites the ticket, a comment and a meeting."></a><br>
  29. <strong>Ask about a ticket.</strong> The answer cites the ticket, a comment and a meeting.
  30. </td>
  31. <td width="50%" valign="top">
  32. <a href=".github/readme/meeting-assistant.png"><img src=".github/readme/gallery/meeting-assistant.png" width="400" alt="A meeting with its summary, action items and transcript, and the assistant beside it answering what was agreed, with the meeting and a ticket as sources"></a><br>
  33. <strong>Ask about a meeting.</strong> Summary, action items and transcript next to the answer.
  34. </td>
  35. </tr>
  36. <tr>
  37. <td width="50%" valign="top">
  38. <a href=".github/readme/board.png"><img src=".github/readme/gallery/board.png" width="400" alt="The tickets of a project as a board with the columns New, In Progress and Resolved"></a><br>
  39. <strong>Tickets as a board</strong> or a list, with your own statuses per project.
  40. </td>
  41. <td width="50%" valign="top">
  42. <a href=".github/readme/time.png"><img src=".github/readme/gallery/time.png" width="400" alt="The time list of the week: hours per person and ticket, day by day"></a><br>
  43. <strong>Time tracking per ticket.</strong> Every session billable on its own.
  44. </td>
  45. </tr>
  46. </table>
  47. Click a picture for the full size. The pictures show the same invented company as the
  48. [live demo](https://demo.lalabase.com).
  49. In production for customers since September 2025. This repository starts with the first public
  50. release, 2026.10.0; [more under Status](#status). If Lalabase is useful to you, a star helps
  51. others find it.
  52. ## What it does
  53. - **Clients and projects.** One organisation per client, any number of projects below it.
  54. Clients get their own access, and roles decide what they see.
  55. - **Tasks.** As a list or a board, with the statuses, priorities and fields you define per
  56. project.
  57. - **Time tracking.** Several sessions per ticket, each one billable on its own, with exports
  58. for the invoice.
  59. - **Documentation.** Notes and documents in the project, and a folder in your GitHub or GitLab
  60. repository becomes the project's docs.
  61. - **Meetings.** Transcript, AI summary and the tasks that follow from it.
  62. - **AI assistant.** One question across tickets, docs, time and meetings, or about the one ticket
  63. or meeting you are looking at, answered with its sources.
  64. - **Your data, your AI.** The AI stays off until you switch it on. Then you pick the provider:
  65. OpenAI, Anthropic, Google Gemini through Vertex AI in the EU, Mistral, IONOS, OVHcloud, or any
  66. OpenAI-compatible endpoint, including a model in your own network. No project data goes to a
  67. provider you did not choose.
  68. - **MCP server and REST API.** Connect Claude, Cursor or your own agent with a personal access
  69. token: list, create and update tickets, comment, log time, search the knowledge base, read the
  70. inbox, and look things up in the indexed code of your repositories.
  71. - **Terminal client.** [Lalabase CLI](https://github.com/lalabase/lalabase-cli) is a separate
  72. program for macOS and Linux, for people who live in the terminal: work through the inbox, read
  73. and answer tickets, book time, hand a ticket to Claude Code and keep an eye on the running agents.
  74. ## Built with
  75. Rails 8.1 on Ruby 4, PostgreSQL with pgvector for the assistant's search, Hotwire (Turbo and
  76. Stimulus) with ViewComponent and Tailwind, and no React. Background jobs run on Solid Queue.
  77. Non-trivial writes go through command objects (`app/services/actors/`), tenants are kept apart
  78. with `acts_as_tenant`, and the project's own rules are enforced by guard specs in CI
  79. (`spec/architecture/`) rather than by review comments. More in [DEVELOPMENT.md](DEVELOPMENT.md).
  80. ## Who it is for
  81. Software agencies, freelancers and small software companies that work on projects for clients
  82. and want their project data, and the AI that works on it, under their own control. Lalabase
  83. replaces the usual mix of ticket tool, wiki, time tracking, chat and reporting spreadsheets.
  84. Most teams come from Redmine, Jira, OpenProject, Asana or spreadsheets. The website
  85. [compares Lalabase with each of them](https://lalabase.com/en/comparison), starting with what
  86. the other tool does well.
  87. ## Two ways to run it
  88. | | Your own server | Our cloud |
  89. |---|---|---|
  90. | Cost | Free under AGPL-3.0. You pay for the server. | Monthly, see [pricing](https://lalabase.com/en/pricing) |
  91. | Operation, updates, backups | You | Us, hosted in Germany, with a DPA |
  92. | Features | All of them, with each release | All of them, always current |
  93. | AI | Your own key or your own model | The provider you choose |
  94. ### Self-host with Docker
  95. You need a server with at least 2 vCPU, 4 GB RAM and 20 GB disk, Docker 24 or later with
  96. Docker Compose v2, and a domain pointing at it.
  97. ```bash
  98. git clone https://github.com/lalabase/lalabase.git && cd lalabase
  99. git checkout "$(git describe --tags --abbrev=0)" # the latest release, not main
  100. cp .env.docker.example .env # fill in the values it asks for
  101. docker compose up -d # pulls the image of that release
  102. docker compose exec web bin/rails lalabase:setup
  103. ```
  104. `compose.yml` starts the application, a job worker, PostgreSQL with pgvector, Valkey and Caddy,
  105. which fetches a TLS certificate for `LALABASE_HOST`. If a proxy of your own terminates TLS, drop
  106. the `COMPOSE_PROFILES=tls` line. Each release has an image `ghcr.io/lalabase/lalabase:<version>`
  107. for linux/amd64 and linux/arm64, and the `compose.yml` of the release pulls it. To build the image
  108. from your checkout instead, use `compose.build.yml` (see its first lines).
  109. The guide covers installation, configuration, AI keys, backups and updates, in English and
  110. German: [lalabase.com/docs](https://lalabase.com/docs/en/self-hosting/getting-started/overview).
  111. We help with the installation on request: hello@lalabase.com.
  112. ### Try it on your own computer
  113. The same steps work without a server, a domain or a mail account. In `.env`, fill in the keys
  114. and the database password as the file describes, then change three things:
  115. ```bash
  116. LALABASE_HOST=localhost:3000
  117. LALABASE_FORCE_SSL=false
  118. # and delete the line COMPOSE_PROFILES=tls
  119. ```
  120. After `lalabase:setup`, sign in at <http://localhost:3000/admin> and create your first user
  121. there. A user created by the admin needs no confirmation mail, so the mail settings can stay as
  122. they are.
  123. ## Status
  124. Lalabase has been developed since October 2024: more than 2,300 commits and about 970 pull
  125. requests, in production for customers since September 2025. This repository starts with the first
  126. public release, 2026.10.0. The earlier history stays private, because it holds customer data
  127. and details of our servers. Development continues here, in the open.
  128. ## License and contributing
  129. Lalabase is licensed under the **GNU Affero General Public License, version 3 only**
  130. (SPDX: `AGPL-3.0-only`). Later versions of the license do not apply unless a release says so.
  131. The full license text is in [LICENSE](LICENSE). Code from invited contributors is also available
  132. under the [Apache License 2.0](LICENSES/Apache-2.0.txt); their commits end with the line
  133. `License: Apache-2.0`.
  134. Bug reports, ideas and questions are always welcome as issues. Unsolicited pull requests are
  135. not accepted: in other projects we have seen that, since AI coding assistants, outside pull
  136. requests take more work to review and fold in than the change itself. The code comes from the
  137. maintainer and a few people we invite. An issue that describes the problem helps most. Details in
  138. [CONTRIBUTING.md](CONTRIBUTING.md#issues-yes-unsolicited-pull-requests-no).
  139. Bundled third-party components keep their own licenses, listed in
  140. [THIRD_PARTY_NOTICES.txt](THIRD_PARTY_NOTICES.txt).
  141. The license covers the code, not the name or the logo. A modified version or a service built on it
  142. goes by its own name: [TRADEMARKS.md](TRADEMARKS.md).
  143. The license covers the code. It grants no rights to the name Lalabase, and none to Lala, the
  144. mascot in `.github/readme/lala-*.svg`: the figure is not covered by the AGPL, all rights are
  145. reserved, and it may not be copied, modified or used outside this repository.
  146. Working on the code: stack, setup, releases and where things live are in
  147. [DEVELOPMENT.md](DEVELOPMENT.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.