App Platform

Apps for Lombok

Extend your Lombok instance with modular apps — install from the app store or build and ship your own on the Lombok app platform.

A platform, not just a plugin API

Lombok's app platform lets you build highly custom app experiences without reinventing the wheel. Authentication, data persistence, background tasks, notifications, and a component library come out of the box — so apps focus on their idea, not their infrastructure.

Embedded UIs

Top-level app screens and alternate explorer views that feel like a core part of the platform.

Multi-platform view layer

One platform-agnostic UI definition renders across iOS, macOS, tvOS, PC, and Android clients.

Serverless handlers

Lightweight TypeScript task & request handlers on schedules, or as system and app event hooks.

Docker worker orchestration

Heavy or non-standard workloads run as container profiles the platform orchestrates for you.

MCP tool hosting

Declare tools in app config and let Lombok handle authentication and authorization via MCP.

Postgres + pgvector

An isolated Postgres schema with pgvector and pg_trgm — bring your own ORM or use Drizzle.

Built for AI

Apps are a great fit for AI generation

Apps are small, well-scoped, and backed by platform primitives — so a coding agent doesn't have to reinvent auth, storage, or task infrastructure to ship something real. Have a product in your workflow that's letting you down? Have your coding agent build a replacement, using our app-development docs and checklists to keep it on track.

Two camps of apps

Apps generally fall into two groups, depending on whether they're built for one team or meant to be shared with everyone.

Custom apps

Custom-built for internal or team-specific use cases. The escape hatch that lets you extend and integrate Lombok without limit — glue it to your stack, model your own workflows, ship exactly what your team needs.

  • Invoices
  • Onboarding Flow
  • Ops Dashboard

Ecosystem apps

Generically useful apps meant to be shared and distributed across instances. These come in three types — first-party, approved third-party, and general third-party — detailed just below.

  • Lombok Files
  • Stripe Sync
  • Kanban

Three types of ecosystem app

Ecosystem apps differ by who builds them, who stands behind them, and how they reach your instance.

First-party

Built & supported by Lombok

Lombok-branded apps created and maintained by the Lombok team, held to the same bar as the core platform.

  • Lombok Files
  • Lombok Chat

Third-party — general

Community-built, opt-in

Community apps with no Lombok involvement. Requires explicitly opting-in the developer's repository as a source, and isn't eligible for the purchase rails.

  • Homelab Tools
  • Niche Importer
  First-partyApprovedGeneral
Built by Lombok Community Community
Supported by Lombok Community Developer
In app store by default
Requires source opt-in
Purchase-rails eligible

“General” apps require adding the developer's repository as a source before they'll appear in your instance.

Where we're taking the ecosystem

The app ecosystem is early. Here's what we're building toward.

01

Stimulate prolific app creation

Make building and shipping an app so low-friction that the ecosystem fills itself out.

02

Ship free first-party apps

A handful of high-quality, free first-party apps that showcase what the platform can do.

03

Offer select paid apps

Possibly one or two paid first-party apps for teams that want more out of the box.

04

Build the app payment system

Payment rails powering paid first-party apps and approved third-party apps alike.