LumbridgeCorp
Contact us
Explore LumbridgeCorpLumbridgeCorp

Open source · Rust · Self-hosted · San Francisco

· LumbridgeCorp

Opening all twelve parts

All twelve repositories open together on November 13, 2026. The test each one has to pass, and where the most work is left.

3 min read5 sections

Lumbridge is twelve parts in twelve repositories, and all twelve open on the same day.

The source opens on November 13, 2026 at github.com/lumbridge-corp. The first plan was one repository at a time from December 24. We moved the date up and open them together. This post says what ready means and which parts have the most work left.

One repository per part

Each part has its own repository, named after it: lumbridge-core, lumbridge-notes, lumbridge-mail and so on. Each has its own page on this site, its own docs and its own “Not yet” list. Each is licensed Apache-2.0.

This matches how the system is used. Parts install and run on their own. The App and Mobile need Core underneath; everything else stands alone. You should be able to take one part and ignore the rest.

The test: a stranger and a clean Ubuntu machine

The test for each repository: someone who has never met us can install that part on a clean Ubuntu machine by following the README. In practice that means four things.

  • The build runs from a fresh clone, with every system package listed.
  • Defaults point at the local machine or at nothing, never at our servers.
  • Sample configs and test data are made up, not copies of our own setup.
  • The LICENSE file and the third-party notices are in place.
FIG. 1The test a repository passes before it opens.Drawn figure

We run our company on this stack every day, and it shows in the code. Some defaults are our addresses. Some sample files describe our machines. That is fine for us and useless to you, so it gets fixed before a part opens.

Why all at once

The parts lean on each other. The App and Mobile need Core underneath. The TUI builds against Notes for its notebook drawer. Mods only makes sense next to the App. Opening them on one day means no public part points at a private one.

Notes, built from a checkout of its repository. These are the commands on its page.
cargo install --path .
lumbridge-notes --dir ~/work-notes
lumbridge-notes ~/work-notes/plan.md
Lumbridge Notes
Lumbridge Notes editing a meeting note with headings, a numbered list, inline code, checked and open tasks and a quote rendered in place, while the line under the cursor shows its Markdown sourceLumbridge Notes editing a meeting note with headings, a numbered list, inline code, checked and open tasks and a quote rendered in place, while the line under the cursor shows its Markdown source
A note is one Markdown file. Only the line you are on shows its source.Open full sizeOpen full size

Until November 13

Until then every repository is private: named on this site with its state, but not readable. If you want a part before then, ask through the contact form at /apply. Say which part you want and what machines you have. A person replies.

Where the most work is left

Three parts need product work, not cleanup. They open with the rest, and we would rather say so now.

  • Library. The deploy script is written for one host, author names are fixed in code, and there is one shared token for all readers. It needs real configuration and an install path.
  • Factory. Gitea is the only code host it supports. There is no installer; a new instance is host scripts and an install log you adapt by hand.
  • Mobile. The data model is one person and their agents, the gateway has not been renamed to Lumbridge yet, and the iOS app compiles but is not signed.

All three are in daily use here. Expect to adapt them by hand, and read each one’s “Not yet” list before you plan around it.

All postsStart the guideContact us