Llumic

We build tools

developers want to use

and businesses

can rely on.

01 / What we build

Developer-friendly business software. POS systems, team management tools, and whatever comes next — built to be extended, not locked in.

02 / How we build

Open foundations. ERPNext, Frappe. Flat pricing. No feature gating by tier. If you pay, you get everything. If you contribute, even better.

03 / Why it matters

Most business software is extractive. We want to build tools that feel like they're on your side — not tools designed to maximize ARPU at the expense of users.

Founders

Two engineers. One obsession.

RA

Rahul Agrawal

Co-founder, Llumic

Builds the products and shapes the product thinking. Rahul has spent years working with ERPNext and Frappe — he knows where business software fails and exactly why.

ERPNext Product Frappe
MD

Manish Dadsena

Co-founder, Llumic

Deep in the engineering side. Manish brings the technical rigor that keeps Llumic's products fast, stable, and scalable when things get real.

Engineering Systems Infrastructure
Philosophy

How we think about software.

01

Pricing should be honest.

Per-user pricing is a tax on growth. It punishes you for hiring. It creates friction at exactly the moment a product should feel liberating. We charge for the product, not for seats.

02

Open foundations, not proprietary cages.

We build on ERPNext and Frappe — open-source, extensible, widely deployed. Your data is yours. Your customizations are yours. You can always see the code beneath the code.

03

Developers are the primary users.

Business software usually ignores developers. We don't. APIs matter. CLI access matters. Scriptability matters. If a developer can't reason about the system, the business can't either.

04

Design is a product decision, not a cosmetic one.

A POS that slows down a cashier costs money every hour. A task tool that obscures team health causes real burnout. We invest in design because bad UX has real consequences.

Engineering culture
Ship small, ship often. Working software over perfect architecture.
No feature that exists only to appear in a demo.
Every performance regression is a bug, not a tradeoff.
Build on what exists. Don't reinvent what Frappe or ERPNext already solved.
Keyboard shortcuts are a product feature, not an easter egg.
If it needs documentation to be usable, the UX needs work.
Stack
Frappe Framework for backend
ERPNext as the ERP backbone
Vue.js for reactive frontends
Python + MariaDB
Self-hostable or cloud-deployed
What we're building

Start with Polo POS
or Hive today.

Both products are actively developed and used in production. Join the businesses that've moved on from legacy software.