lomi.

Open source

lomi. publishes integrator tooling and documentation as open source. Payment processing runs on our hosted platform, not as a self-hosted product today.

lomi. follows a hosted-first model. Merchants integrate via our cloud API, dashboard, and checkout. We are not offering self-hosted payment processing at this time.

Our long-term direction is to open the monorepo progressively, more apps, more source, and eventually a supported path for operators who self-host with their own provider agreements and compliance. That future state is not available yet; see Roadmap for what is public today.

We still publish source for transparency and for integrator tooling (SDKs, CLI, plugins, docs). In line with that vision, we follow a dual-license approach.

Our project is primarily licensed under the GNU Affero General Public License (AGPL), allowing the open-source community to freely use, modify, and redistribute our software. However, the AGPL requires that anyone using the software, especially when providing it as a service, must also make the source code available to the public. Therefore, if you wish to use lomi. without sharing your modifications, i.e. incorporating it into closed-source products, or use it commercially to offer similar products or services, a commercial license is required.

Certain components are covered exclusively by our commercial license, designed for businesses that need additional features or usage flexibility. This dual-licensing model lets us serve both the open-source community and enterprise partners.

See the monorepo LICENSE file for the complete terms of both licenses.

What is open source today?

AreaAvailability
Hosted payment platform (API, dashboard, checkout, compliance)Production, sign up
API and webhooksHosted only
SDKs, CLI, MCP, pluginsIntegrator tooling (source + packages)
Documentation websiteOpen source (apps/docs)
Merchant dashboard, checkout, storefrontHosted product (source opening progressively)
AdminProprietary

Not self-hostable today. Running payment processing requires lomi.’s hosted infrastructure, payment partner agreements, compliance coverage, and operational stack. Local clones are for development and contribution, not for operating your own payment processor.

Hosted platform

For production payments, use the hosted platform on dashboard.lomi.africa. You get built-in payment channels, payment partner agreements and compliance coverage, automatic updates, and dedicated support.

Quick comparison

FeatureOpen-source toolingHosted platform
API and webhooksIntegrate against hosted APIYes
Built-in payment channels-Yes
Merchant dashboard and checkout-Yes
SDKs, CLI, MCP, pluginsSource + packagesYes
Self-hosting the payment stackOn the roadmap-
Automatic updates-Yes
Dedicated supportCommunityYes

Support options

The hosted platform includes:

  • 24/7 technical support
  • Priority issue resolution
  • Implementation assistance

Resources

Roadmap

We are progressively open-sourcing the monorepo. Self-hosting the full payment stack is a long-term objective, not something we support in production today. The path looks like: publish more source → document operator requirements (providers, partner agreements, compliance) → offer a supported self-host option when the stack is complete and safe to run without lomi.’s hosted services.

What is open today:

  • Currently open source:

    • Documentation website: apps/docs (this site)
    • CLI (apps/cli), integrator tool; build on the hosted API, not platform ops
    • API service: apps/api
    • SDKs: apps/sdks
    • E-commerce plugins: separate repos under apps/plugins/, woo, magento, prestashop, shopify, bubble
    • MCP server (apps/mcp), integrator tool; merchant API in your IDE, not platform ops
    • Agent plugin (apps/tools/agent-plugin), marketplace packaging for hosted MCP; lomiafrica/agent-plugin
    • Events boilerplate (separate repo): lomiafrica/events
  • Opening soon:

    • Merchant dashboard: apps/dashboard
  • Proprietary:

    • Admin dashboard: apps/admin
  • Hosted product (source not fully public yet):

    • Checkout: apps/checkout
    • Storefront: apps/storefront
    • Customer portal: apps/customers
    • Marketing website: apps/website

Many files, especially database migrations and core payment logic, are marked /* @proprietary license */ even inside AGPL-licensed apps.

Monorepo layout

└── lomi./
    ├── README.md
    ├── CONTRIBUTING.md
    ├── LICENSE
    ├── pnpm-workspace.yaml
    ├── tooling/          # shared eslint, knip, tsconfig, postcss, scripts (not a package)
    ├── packages/
    │   ├── ui/           # @lomi./ui — shared React primitives (workspace-internal)
    │   ├── shared/       # @lomi./shared — format helpers, json-value, generated Database types
    │   ├── queries/      # @lomi./queries — injected RPC wrappers
    │   ├── pay/          # @lomi./pay — hosted checkout/storefront form chrome (React 19)
    │   └── receipt-pdf/  # @lomi./receipt-pdf — receipt PDF (workspace-internal)
    └── apps/
        ├── admin/        # Internal admin (proprietary)
        ├── api/          # NestJS payment API (open source)
        ├── checkout/     # Hosted checkout (hosted product)
        ├── cli/          # Rust CLI (integrator tool; open source)
        ├── customers/    # Customer portal (hosted product)
        ├── dashboard/    # Merchant dashboard (opening soon)
        ├── design/       # Shared design assets
        ├── docs/         # Developer documentation (open source, this app)
        ├── pos/          # lomi. merchant phone app
        ├── mcp/          # MCP server (integrator tool; open source)
        ├── plugins/      # WooCommerce, Magento, PrestaShop, Shopify, Bubble, references
        ├── sdks/         # TypeScript, Python, PHP, Go SDKs (open source)
        ├── storefront/   # Merchant storefront (hosted product)
        ├── tools/        # Independent tools (agent-plugin, gsc-mcp, anti-slop, …)
        └── website/      # Marketing site (hosted product)

Merchant dashboard (apps/dashboard)

The dashboard is the merchant back-office (transactions, payment links, settings, analytics). It is a hosted product today; source is opening progressively.

High-level layout:

└── apps/dashboard/
    ├── package.json
    ├── .env.example
    ├── src/              # React app (Vite)
    ├── supabase/         # Canonical DB migrations and edge functions
    │   └── migrations/
    └── public/           # Static assets

Database migrations under supabase/migrations/ are the schema source of truth for the platform. They are not a recipe for running your own payment stack without lomi.’s hosted services and provider agreements.

Contributing

We welcome contributions to open-source areas and documentation. Open an issue or submit a pull request on the lomi. monorepo.

Before contributing:

  1. Read our Code of Conduct
  2. Review our Security Policy
  3. Do not modify files marked with /* @proprietary license */

See Contributing and the monorepo CONTRIBUTING.md.

Need help deciding?

If you have questions about open source vs the hosted platform, contact hello@lomi.africa.

To learn more about our vision, visit our blog or use the pricing tool.

On this page