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.
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
Markdown
[](/listings/lalabase--lalabase)HTML
<a href="/listings/lalabase--lalabase"><img src="/api/listings/lalabase--lalabase/badge.svg" alt="findsafeskills safety rating" /></a>Install
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.
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset=".github/readme/lala-assistant-dark.svg">
- <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.">
- </picture>
- </p>
- <h1 align="center">Lalabase</h1>
- <p align="center">
- <strong>A self-hosted project brain for devs and customers.</strong><br>
- <sub>RUBY ON RAILS · POSTGRESQL</sub>
- </p>
- <p align="center">
- <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>
- <a href="LICENSE"><img src="https://img.shields.io/badge/license-AGPL--3.0--only-blue" alt="License: AGPL-3.0-only"></a>
- <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>
- <a href="https://demo.lalabase.com"><img src="https://img.shields.io/badge/demo-live-brightgreen" alt="Live demo"></a>
- </p>
- Tickets, time tracking, docs and meetings for software agencies and their clients, with an AI
- assistant that answers from your own project data and cites its sources. Free on your own server,
- or hosted by us in Germany.
- **[Try the live demo](https://demo.lalabase.com)**: no sign-up, the login is on the page, and
- everything resets every night.
- [Website](https://lalabase.com/en) · [Self-hosting](https://lalabase.com/docs/en/self-hosting/getting-started/overview) ·
- [Cloud pricing](https://lalabase.com/en/pricing) · [Changelog](CHANGELOG.md)
- <table>
- <tr>
- <td width="50%" valign="top">
- <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>
- <strong>Ask about a ticket.</strong> The answer cites the ticket, a comment and a meeting.
- </td>
- <td width="50%" valign="top">
- <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>
- <strong>Ask about a meeting.</strong> Summary, action items and transcript next to the answer.
- </td>
- </tr>
- <tr>
- <td width="50%" valign="top">
- <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>
- <strong>Tickets as a board</strong> or a list, with your own statuses per project.
- </td>
- <td width="50%" valign="top">
- <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>
- <strong>Time tracking per ticket.</strong> Every session billable on its own.
- </td>
- </tr>
- </table>
- Click a picture for the full size. The pictures show the same invented company as the
- [live demo](https://demo.lalabase.com).
- In production for customers since September 2025. This repository starts with the first public
- release, 2026.10.0; [more under Status](#status). If Lalabase is useful to you, a star helps
- others find it.
- ## What it does
- - **Clients and projects.** One organisation per client, any number of projects below it.
- Clients get their own access, and roles decide what they see.
- - **Tasks.** As a list or a board, with the statuses, priorities and fields you define per
- project.
- - **Time tracking.** Several sessions per ticket, each one billable on its own, with exports
- for the invoice.
- - **Documentation.** Notes and documents in the project, and a folder in your GitHub or GitLab
- repository becomes the project's docs.
- - **Meetings.** Transcript, AI summary and the tasks that follow from it.
- - **AI assistant.** One question across tickets, docs, time and meetings, or about the one ticket
- or meeting you are looking at, answered with its sources.
- - **Your data, your AI.** The AI stays off until you switch it on. Then you pick the provider:
- OpenAI, Anthropic, Google Gemini through Vertex AI in the EU, Mistral, IONOS, OVHcloud, or any
- OpenAI-compatible endpoint, including a model in your own network. No project data goes to a
- provider you did not choose.
- - **MCP server and REST API.** Connect Claude, Cursor or your own agent with a personal access
- token: list, create and update tickets, comment, log time, search the knowledge base, read the
- inbox, and look things up in the indexed code of your repositories.
- - **Terminal client.** [Lalabase CLI](https://github.com/lalabase/lalabase-cli) is a separate
- program for macOS and Linux, for people who live in the terminal: work through the inbox, read
- and answer tickets, book time, hand a ticket to Claude Code and keep an eye on the running agents.
- ## Built with
- Rails 8.1 on Ruby 4, PostgreSQL with pgvector for the assistant's search, Hotwire (Turbo and
- Stimulus) with ViewComponent and Tailwind, and no React. Background jobs run on Solid Queue.
- Non-trivial writes go through command objects (`app/services/actors/`), tenants are kept apart
- with `acts_as_tenant`, and the project's own rules are enforced by guard specs in CI
- (`spec/architecture/`) rather than by review comments. More in [DEVELOPMENT.md](DEVELOPMENT.md).
- ## Who it is for
- Software agencies, freelancers and small software companies that work on projects for clients
- and want their project data, and the AI that works on it, under their own control. Lalabase
- replaces the usual mix of ticket tool, wiki, time tracking, chat and reporting spreadsheets.
- Most teams come from Redmine, Jira, OpenProject, Asana or spreadsheets. The website
- [compares Lalabase with each of them](https://lalabase.com/en/comparison), starting with what
- the other tool does well.
- ## Two ways to run it
- | | Your own server | Our cloud |
- |---|---|---|
- | Cost | Free under AGPL-3.0. You pay for the server. | Monthly, see [pricing](https://lalabase.com/en/pricing) |
- | Operation, updates, backups | You | Us, hosted in Germany, with a DPA |
- | Features | All of them, with each release | All of them, always current |
- | AI | Your own key or your own model | The provider you choose |
- ### Self-host with Docker
- You need a server with at least 2 vCPU, 4 GB RAM and 20 GB disk, Docker 24 or later with
- Docker Compose v2, and a domain pointing at it.
- ```bash
- git clone https://github.com/lalabase/lalabase.git && cd lalabase
- git checkout "$(git describe --tags --abbrev=0)" # the latest release, not main
- cp .env.docker.example .env # fill in the values it asks for
- docker compose up -d # pulls the image of that release
- docker compose exec web bin/rails lalabase:setup
- ```
- `compose.yml` starts the application, a job worker, PostgreSQL with pgvector, Valkey and Caddy,
- which fetches a TLS certificate for `LALABASE_HOST`. If a proxy of your own terminates TLS, drop
- the `COMPOSE_PROFILES=tls` line. Each release has an image `ghcr.io/lalabase/lalabase:<version>`
- for linux/amd64 and linux/arm64, and the `compose.yml` of the release pulls it. To build the image
- from your checkout instead, use `compose.build.yml` (see its first lines).
- The guide covers installation, configuration, AI keys, backups and updates, in English and
- German: [lalabase.com/docs](https://lalabase.com/docs/en/self-hosting/getting-started/overview).
- We help with the installation on request: hello@lalabase.com.
- ### Try it on your own computer
- The same steps work without a server, a domain or a mail account. In `.env`, fill in the keys
- and the database password as the file describes, then change three things:
- ```bash
- LALABASE_HOST=localhost:3000
- LALABASE_FORCE_SSL=false
- # and delete the line COMPOSE_PROFILES=tls
- ```
- After `lalabase:setup`, sign in at <http://localhost:3000/admin> and create your first user
- there. A user created by the admin needs no confirmation mail, so the mail settings can stay as
- they are.
- ## Status
- Lalabase has been developed since October 2024: more than 2,300 commits and about 970 pull
- requests, in production for customers since September 2025. This repository starts with the first
- public release, 2026.10.0. The earlier history stays private, because it holds customer data
- and details of our servers. Development continues here, in the open.
- ## License and contributing
- Lalabase is licensed under the **GNU Affero General Public License, version 3 only**
- (SPDX: `AGPL-3.0-only`). Later versions of the license do not apply unless a release says so.
- The full license text is in [LICENSE](LICENSE). Code from invited contributors is also available
- under the [Apache License 2.0](LICENSES/Apache-2.0.txt); their commits end with the line
- `License: Apache-2.0`.
- Bug reports, ideas and questions are always welcome as issues. Unsolicited pull requests are
- not accepted: in other projects we have seen that, since AI coding assistants, outside pull
- requests take more work to review and fold in than the change itself. The code comes from the
- maintainer and a few people we invite. An issue that describes the problem helps most. Details in
- [CONTRIBUTING.md](CONTRIBUTING.md#issues-yes-unsolicited-pull-requests-no).
- Bundled third-party components keep their own licenses, listed in
- [THIRD_PARTY_NOTICES.txt](THIRD_PARTY_NOTICES.txt).
- The license covers the code, not the name or the logo. A modified version or a service built on it
- goes by its own name: [TRADEMARKS.md](TRADEMARKS.md).
- The license covers the code. It grants no rights to the name Lalabase, and none to Lala, the
- mascot in `.github/readme/lala-*.svg`: the figure is not covered by the AGPL, all rights are
- reserved, and it may not be copied, modified or used outside this repository.
- Working on the code: stack, setup, releases and where things live are in
- [DEVELOPMENT.md](DEVELOPMENT.md).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.