L
lalabase/lalabase
Self-hosted project management for devs and their clients: tickets, time tracking, docs and meetings, with an…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 141 ★ · lalabase/lalabase · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 1 sources
- Score
- score 103 · 141 ★ · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
lalabase/lalabase;first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.Lalabase
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
A self-hosted project brain for devs and customers.
RUBY ON RAILS · POSTGRESQL
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: no sign-up, the login is on the page, and
everything resets every night.
Website · Self-hosting ·
Cloud pricing · Changelog
Ask about a ticket. The answer cites the ticket, a comment and a meeting.
Ask about a meeting. Summary, action items and transcript next to the answer.
Tickets as a board or a list, with your own statuses per project.
Time tracking per ticket. Every session billable on its own.
Click a picture for the full size. The pictures show the same invented company as the
live demo.
In production for customers since September 2025. This repository starts with the first public
release, 2026.10.0; more under 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 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 actsastenant, and the project's own rules are enforced by guard specs in CI
(spec/architecture/) rather than by review comments. More in 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.
RUBY ON RAILS · POSTGRESQL
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: no sign-up, the login is on the page, and
everything resets every night.
Website · Self-hosting ·
Cloud pricing · Changelog
Ask about a ticket. The answer cites the ticket, a comment and a meeting.
Ask about a meeting. Summary, action items and transcript next to the answer.
Tickets as a board or a list, with your own statuses per project.
Time tracking per ticket. Every session billable on its own.
Click a picture for the full size. The pictures show the same invented company as the
live demo.
In production for customers since September 2025. This repository starts with the first public
release, 2026.10.0; more under 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 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 actsastenant, and the project's own rules are enforced by guard specs in CI
(spec/architecture/) rather than by review comments. More in 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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/lalabase-lalabase/)
- Source
- github · https://github.com/lalabase/lalabase
- Browse by field
- Open source
- Traction
- 141 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.