Multi-app platform · Made in India
Udyamik runs the small businesses of small-town India on one platform. Each organisation gets its own database schema and its own screens. Each person gets one account, one document vault and one feed, and keeps all three when they leave.
Switch the organisation in the console and watch what changes: the navigation, the schema answering, the records on the canvas. What does not change is who you signed in as.
No credit card · no passwords anywhere, an OTP and a device PIN instead
Built on
In queue
4
longest 22 min
Seen
11
since 09:00
Walk-in
7
of 15 today
Collected
8,450
OPD, rupees
| Token | Patient | UHID | Age / Sex | Slot | Doctor | Status |
|---|---|---|---|---|---|---|
| A-014 | Ramesh Kumar | UH-00241 | 54 / M | 09:40 | Dr Iyer | In consultation |
| A-015 | Lakshmi Narayan | UH-00118 | 61 / F | 09:55 | Dr Iyer | Waiting |
| A-016 | Mohammed Irfan | UH-00907 | 33 / M | 10:10 | Dr Iyer | Waiting |
| B-004 | Anita Desai | UH-00452 | 29 / F | 10:10 | Dr Rao | Billing |
| B-005 | Suresh Babu | UH-01330 | 47 / M | 10:25 | Dr Rao | Waiting |
| A-013 | Geetha Krishnan | UH-00076 | 38 / F | 09:25 | Dr Iyer | Done |
| B-003 | Nagaraj Gowda | UH-00689 | 66 / M | 09:55 | Dr Rao | Done |
Find patient: mobile number, UHID, or name. One box for all three, we search whatever you type.
The real workspace switcher. Three organisations, three schemas, one account.
Each App owns its own schema, its own roles and its own screens. They share identity, documents, notifications, billing and audit, so a second App does not mean a second login for your staff or a second account for the people you serve, and a person who belongs to three of them still has one login.
School operations
Admissions, fees, attendance, exams and report cards, with a parent portal and WhatsApp dispatch on top. Everything bound to one academic session, so last year stays readable and this year stays correct.
schema edu · schools
Daily-wage lendingऋणसाथी
For the lender the formal banking system leaves alone: small cash loans to daily-wage borrowers, repaid in daily installments, collected door to door by an agent with a notebook.
schema lending · village and small-town lenders
Ask your own dataसहायक
Natural-language questions against your own records: fees outstanding, attendance dips, the admissions pipeline. Quota-metered and audit-logged, so an AI feature cannot quietly become an AI bill.
an add-on, with no schema of its own · admins on any app
OPD, EMR, e-prescription
Registration with a UHID, a walk-in queue, template-driven vitals, an NMC-compliant e-prescription, and the part that is unusual: the patient keeps their own copy.
schema clinic · out-patient clinics and small hospitals
Retail chemist ERP
Batch and expiry on every bill line, FEFO at the counter, loose units, a Schedule H1 register written as you sell, cash and bank books with a day close, GSTR-1 and GSTR-3B, and a shared list of 245,140 medicines so a new shop does not type its catalogue.
schema pharmacy · retail chemists
General store billing and stockStockसाथी
A counter that bills by barcode, by weight or by name, stock kept as a ledger of every movement, a khata per customer and supplier, cash and bank books with a day close, and GSTR-1 and GSTR-3B per GSTIN. Every shop of a business has its own GSTIN and bill series.
schema retail · kirana, auto parts, hardware and electronics shops
Pathology lab (LIMS)
Accession and barcode, the full sample custody chain, analyzer interfacing, pathologist authorisation and report delivery. Sellable to a lab with no clinic attached.
schema lab · pathology labs and diagnostic centres
Your family’s medical record
Not an App you subscribe to: a part of your own account. Your family tree, each member’s reports filed by subject, lab values trended against the range the lab itself printed, a medication timeline, and a health card you can hand to a hospital that has never heard of us.
schema public · anyone, no organisation required
A gym, a coworking desk, a tuition centre. The identity, auth, org, feed and storage layers are already built, so a new vertical is its own schema, its own roles and its own screens, and nothing underneath has to be reshaped.
Every generic SaaS dashboard ships the same defaults. We picked the ones a school in a tier-3 town, a lender in a village and a two-doctor clinic actually need, and rejected the ones they do not.
Native integrations rather than US-first tools retrofitted. Phone numbers stored as ten local digits. One price per App, the same whichever you run. Immunization charts from UIP and IAP, not the CDC schedule.
Every sign-in is an OTP; every cold launch on a trusted device is a four to six digit PIN tied to that device. No reset flow, no credential stuffing, no support ticket about a forgotten password.
A parent at a school, a borrower at a lender, a patient at a clinic. Same login, same feed, same document vault, and often the same person, which is the whole point.
Read a row rather than a column. The platform supplies each of these once, and every App spends it differently. That is the whole of why a vertical here takes months rather than years, and why a person who belongs to four of them still has one account.
| Supplied once | School edu | Lender lending | Clinic clinic | Chemist pharmacy |
|---|---|---|---|---|
| One identity public.users | A parent | A borrower | A patient | A customer with a khata |
| One document vault public.user_documents | Marksheet, transfer certificate | KYC pack, signed agreement | Prescription, discharge note | Prescription against an H1 sale |
| One notification meter counted before the send | Fee due, absence, report card | Installment receipt, overdue | Prescription, follow-up | Bill link, refill reminder |
| One audit log before and after, per change | Fee waiver, role change, publish | Disbursal, write-off | Prescription issued | Expired-batch write-off |
| Its own schema row-level security on every table | edu | lending | clinic | pharmacy |
Cross-App reads go through the other App's service or a published event, never a SQL join across schemas. That rule is why the bottom row can say four different things and still be safe.
Your account · schema public
Most business software makes the organisation the primary record and the person a foreign key. Udyamik is built the other way round. There is a person plane that belongs to you and a tenant plane that belongs to each organisation, and they are different schemas on purpose.
A child's immunization record belongs to the family, not to whichever clinic gave the dose. A marksheet belongs to the student, not to the school that printed it. So when you leave, it comes with you.
Your family
A real tree: spouse, parents, children, siblings. Each member carries their own medical history, filed against them rather than into a shared folder.
Your documents
One vault you own. A school gets a pointer to the marksheet, not a copy, so changing school is a new pointer rather than a re-upload.
Your feed
Fees due at one school, a report published at another, an installment recorded at a lender: one chronological surface across every organisation you belong to.
Your record
Academic history and medical history both outlive the organisation that created them. Leaving a school does not delete the marksheet.
Free, and no organisation required
Members
6
three generations
Reports
41
filed by member
Values
312
trended
Medicines
4
ongoing
| Date | Member | Test | Value | Lab's range | Source |
|---|---|---|---|---|---|
| 28 Sep | Self | Fasting glucose | 118 mg/dL | 70 - 100 | Lab PDF |
| 28 Sep | Self | HbA1c | 6.1 % | 4.0 - 5.6 | Lab PDF |
| 28 Sep | Self | Creatinine | 0.9 mg/dL | 0.7 - 1.3 | Lab PDF |
| 14 Sep | Mother | Haemoglobin | 10.4 g/dL | 12.0 - 15.0 | Lab PDF |
| 14 Sep | Mother | Vitamin D | 21 ng/mL | 20 - 50 | Lab PDF |
| 02 Sep | Son, age 7 | Weight | 22.5 kg | - | Self-entered |
| 19 Aug | Self | Fasting glucose | 109 mg/dL | 74 - 106 | Lab PDF |
We reproduce the range the lab printed and never add a verdict of our own.
Each value against the range its own lab printed. Self-entered rows say so.
Data safety
The DPDP Act makes you responsible for losing data, and so does every Indian school we have talked to. The backup pipeline is treated as a feature: documented, rehearsed, and restorable by you without us.
Where the data sits
The database and its backups are in Mumbai and stay there. A WhatsApp message reaches Meta and a Sahayak question reaches a model endpoint, and both are named in the privacy policy. Health records have no third party at all.
Every nightly dump is encrypted with age (AES-256) at the source, using a public key the server only knows how to write with. The matching private key never touches the production machine.
A systemd timer fires the backup in the quietest window: no teacher marking attendance, no parent paying a fee, no admin at a desk. A miss while the box was off is caught up on the next boot.
If we vanished tomorrow, a customer holding the private key could decrypt their dump and stand the database up on any Postgres 16. No proprietary format and no lock-in on the data you trusted us with.
The same figure whichever App you run. An organisation that takes a second App pays it twice, on the same login and the same staff list.
₹500/month
₹4,800/year
per App · per App, per organisation
At this price
6 apps
Your own account, with the family tree, the document vault and the health record, costs nothing and needs no organisation.
Udyamik