Care in Asia is many small participants. So we built the layer that connects them.
Not one large one, digitised. The distinction sounds academic until you try to build software for the first thing using architecture designed for the second — which is what most of this industry has been doing, and why the patient is still the integration layer.
What we build
One engine, ten ERPs, one patient app
Who it is for
Everyone who delivers or receives care
Where it is for
Asia-first, multi-country by design
Nothing here is broken. Everything here is disconnected.
Walk a patient through a single episode of care and count the systems. A clinic registers them. A lab runs a panel and prints it. A pharmacy dispenses against a photograph of a prescription. A hospital admits them and registers them again, because the clinic’s record might as well not exist. Somewhere in there, an ambulance operator gets a phone call.
Each of those participants is competent. Each of their systems, taken alone, mostly works. And the patient still ends up carrying a plastic bag of paper between them, because the connective tissue was never anybody’s product.
Meanwhile the software itself cannot bend. Ask your vendor for one extra field and you get a quote and a timeline. So the field goes in a spreadsheet, and now the truth about your patients lives in two places, and one of them is a laptop.
These are not two problems. They are the same problem, seen from two ends: healthcare software was built as products to be sold, rather than as a system to be joined.
2020 made the gap impossible to ignore
By then you could summon a car, order dinner, move money to another country and sit an exam — all from a phone, all in minutes. An enormous amount of ingenuity had gone into making ordinary life frictionless.
Then the pandemic arrived, and the one thing nobody had connected turned out to be the one thing that mattered. People could not find out which hospital had a bed, whether a lab had capacity, which pharmacy still had stock, or whether an ambulance was actually coming. Not because the answers did not exist — they existed, in a dozen systems that could not see each other. Help was real and simply out of reach, and the information people needed to make decisions did not travel to them in time.
A great many people lived through that. Not everyone did. We are not going to dress that up into a marketing story, and CareSewa would be a poor memorial if it were only a slogan.
What stayed with us is narrower and more useful: the failure was not medical. Clinicians did extraordinary work. The failure was infrastructural — no connective layer, so no shared picture, so no way for the right help to find the right person fast enough. Then the emergency passed, attention moved on, and health went back to being the part of life nobody had wired together.
That is the gap CareSewa exists to close. Not another hospital system — the layer between them all.
By 2020, this was already true
Staying alive
Still a phone call, a paper file, and hoping someone picked up.
Everything else in ordinary life had been connected. The one part that decides whether you live was left as it was.
Why Asia-first is an architecture, not a market
This is the argument the whole company rests on. If it is wrong, everything downstream of it is wrong too — so it is worth stating carefully.
The dominant model of healthcare software was shaped by markets where care consolidated. Large integrated systems own the hospital, the lab, the imaging centre and often the insurer. In that world, the sensible thing to build is a very large system for a very large customer. Integration is an internal problem. Interoperability is a standards committee’s problem. The architecture follows the shape of the market — and the shape is few, big, vertical.
Asia is not shaped like that. Care here is delivered by dense networks of small independent participants: the single-doctor clinic that half a neighbourhood depends on. The standalone lab two streets over. The independent pharmacy that knows its customers by name. The private ambulance operator with four vehicles. The dental practice above the shop. None of them is going to be acquired into a giant, and none of them is waiting to be.
So the winning architecture is not “one large participant, digitised”. It is many small participants, connected — and those are not the same product with different pricing. They are different products.
One large participant, digitised
- Built for a few very large buyers, so it is priced and sold for them
- Implementation is a project measured in quarters and consultants
- Configuration is a change request, because the model is in the codebase
- Integration is somebody else’s standards problem
- A four-vehicle ambulance operator is not a customer. It is a rounding error.
Many small participants, connected
- A two-doctor clinic and a four-hospital group run the same engine
- Live in days. Self-serve. No procurement cycle to survive first.
- Configuration is the product, because the model is data, not code
- Connection is the point, not an afterthought bolted on at version 4
- The small operator is not a rounding error. It is the network.
Follow that thesis and the consequences are not stylistic — they are structural. If your customer is a small independent practice, they cannot survive a six-month implementation, so configuration has to be something they do themselves. If there are thousands of them rather than dozens, no consultant can model each one, so the models must be defined at runtime. If value comes from the network, then connecting must be self-serve and reversible — a marketplace you join and leave, not a contract you are trapped in. And if records travel across many independent participants, then the only coherent owner of a record is the patient, because no single provider is ever going to be the centre.
Every architectural decision in CareSewa falls out of that paragraph. The no-code engine is not a feature we thought was cool. It is what this market’s shape demands.
And Asia is not one country, so we never assumed one
“Asia-first” would be an empty phrase if it meant one national market with ambitions. Every country here has its own identifier schemes, its own record-keeping requirements, its own currency, its own regulatory shape. A platform that hard-codes any one of those is a platform that must be forked to cross a border.
So none of it is hard-coded. What a country requires you to record is a field you define. Prices resolve per market rather than living as a symbol in our source. The stack is deployable per region. Multi-country is not a phase two — it is the reason the engine works the way it does.
Sewa — सेवा
Sewa means service. Not service as in a helpdesk or a service level agreement — service as in the act of caring for another person, offered rather than transacted. It is an old word, and it is not a soft one.
We chose it for two reasons. The first is that it travels: it is recognisable across South and Southeast Asia, in more languages than any of us speak, which is exactly the ground this platform stands on. A name that only worked in one country would have contradicted the thesis on the page above it.
The second is that it is a standard to be held to. Healthcare software has a habit of drifting away from the person it exists for — becoming a billing engine, a compliance artefact, a thing the staff fight with. Putting sewa in the name means the question “does this actually serve someone?” is asked every time anyone says our name out loud.
Care, and the act of serving it. That is the entire product in two syllables.
सेवा
se·wa
noun. service; the act of caring for another. Recognised across South and Southeast Asia.
CareSewa — care, and the serving of it.
The rules we do not negotiate
These are not values on a wall. They are the engineering rules the codebase is actually held to — which is why they read like constraints rather than aspirations.
The engine is the product
Every ERP in the suite is a configuration of one engine. When we improve the engine, all ten get better at once. When we are tempted to special-case one, that is a sign the engine is wrong.
Never hard-code a healthcare model
The moment “Patient” becomes a class in our codebase, every practice on earth inherits our idea of what a patient is. A field is a database record. It has to stay that way.
Tenant isolation is absolute
Not a feature, not a tier, not a configuration. Every definition and record carries a tenant, every query filters by it, and cross-tenant access is explicit or it does not happen.
Defaults are suggestions, not law
We seed sensible models when a portal is provisioned. You are meant to throw them away. Three ERPs ship with no defaults at all, because for those, ours would be wrong for everyone.
Medical data is never destroyed
Records are soft-deleted. Removing a field stops collection but preserves what was recorded. A schema edit must never rewrite clinical history — that rule has no exceptions.
Every mutation is audited
Actor, tenant, action, before, after, IP, timestamp — append-only, editable by nobody. The audit trail is the one thing the no-code engine deliberately cannot reshape.
Every one of these has cost us something to keep.
Reading permissions fresh on every request costs a database read. Refusing to hard-code a patient model costs us the easy demo. Rejecting ambiguous writes costs somebody an error message. A principle you have never paid for is not a principle — it is a preference.
Three things, and they only work together
Factually, this is what exists today. The roadmap is further down, clearly marked as such.
The ERP suite
Hospital, clinic, dental, laboratory, diagnostics, pharmacy, ambulance, blood bank, plus the doctor and patient portals. One account can own one of them or all ten, each entitled on its own, each on its own subdomain. 7 arrive with default models seeded; 3 start deliberately blank, because our defaults would have been wrong for everyone.
See the suiteThe metadata-driven engine
Node, Express, MongoDB and TypeScript underneath; Next.js and Expo on top. Models are defined at runtime across 18 field types with relations, validation and permissions — a field is a database record, not a line of code. Every model you define gets a REST API automatically, with the same envelope and auth as everything else.
How it worksCareSewa One
The patient super-app. One Health ID that belongs to the person, not to a hospital. Connect providers, book across twelve care services from consult to ambulance, carry every record between them, and ask questions of verified clinicians. Connect, share, revoke — consent that is actually enforced.
Explore the appBuilding only the provider half would have made us a software vendor. Building only the patient half would have made us an app with scanned PDFs in it. The whole argument of this company is that the value is in the connection — so the connection had to be the thing we built.
Configuration over consulting
The traditional healthcare software business earns more from the implementation than the licence. That is a structural incentive to keep the product hard to change. We took the opposite bet.
If configuring the system requires us, then every customer is a project, every project needs people, and the company can only grow as fast as it can hire. Worse: we would be quietly rewarded for rigidity, because rigidity is billable.
So we made the product configurable by the person who understands the problem — the practice that actually runs the workflow. Not because it is generous. Because it is the only model that reaches thousands of small independent participants at all.
- You configure it, not us — Studio is the product, not a professional-services tool
- Defaults get you started in minutes and are meant to be thrown away
- If something can only be done by us, we treat that as a bug in the engine
- The API we document is the API our own apps call — no privileged internal path
Ship instantly — the two paths
Schema push
Model changesA model is data. Changing it writes a record, and the very next request renders the new shape. No build, no migration, no release note. Your users are never a version behind because there are no versions to be behind.
Over-the-air updates
App changesThe mobile apps update over the air rather than waiting in an app-store review queue. A fix reaches people the day it is written, not the week it is approved.
Between them, the gap between “we should change that” and “it is changed” collapses from a quarter to an afternoon. That is not a performance optimisation. It is the difference between software that shapes your practice and software your practice shapes.
CareSewa is built by Lacspace
Lacspace is a software company founded in 2021 and built out of South Asia — Kathmandu, Nagpur, Itahari, Biratnagar, Delhi and Patna — shipping platforms to customers well beyond it. Its founder and chairperson, Eallen Karna, states the company’s premise plainly: technology is a right, not a luxury.
That matters here for a reason that is not sentiment. CareSewa is not this company’s first ecosystem — it is roughly its twenty-sixth. Lacspace has already built and run multi-tenant platforms for enterprise ERP, logistics, ticketing, education, retail, accounting and food delivery. Every one of them is the same underlying problem: many independent participants, each with their own way of working, who need to act as one network without surrendering their autonomy.
Health is the hardest instance of that problem, and the one with the highest cost of getting it wrong. It is not a domain you would choose as a first attempt. We came to it having solved the general shape of it, repeatedly, everywhere else first.
The figures below are Lacspace’s own published numbers. We have linked the source rather than asking you to take ours for it.
2021
Founded
26+
Products shipped
100+
Clients
6
Offices
Sibling platforms
lacspace.comCareSewa
Health — the one they had not built yet
A selection. Lacspace publishes 26+ shipped products — the full list is on their site.
Everyone the network is made of
If care in Asia is a network of small independent participants, then the platform cannot be selective about which of them it serves.
Independent practices
Clinics and dental practices that need to open this week, not next quarter. Start blank, model what you actually track, grow into the rest.
Clinic ERPHospitals & groups
Every department, ward and facility under one account, with staff permissions scoped to exactly what each person should touch.
Hospital ERPService operators
Labs, pharmacies, ambulance fleets and blood banks — plug into the hospitals and patients around you instead of waiting to be referred to.
Partner with usPeople
Anyone tired of being their own medical filing system. One Health ID, records that follow you, consent you actually control.
CareSewa OneThe roadmap, labelled as a roadmap
None of the following is shipped. We are listing it because you deserve to know where this is going — and separating it from the section above because a roadmap presented as a feature list is just a lie with a longer fuse.
Everything below is planned, not delivered. No dates, because dates we invented to sound confident would be the first thing on this page to become untrue. Ask us where any of it stands and you will get the real answer.
Deeper health features
Richer clinical surfaces built on the same engine — the primitives are there; the opinionated views on top of them are not, yet.
Family accounts
One person managing care for parents and children, without juggling logins. Family is already a plan tier; the full account model behind it is still ahead of us.
Reminders
Medication, follow-ups, vaccinations. Adherence is where most care actually fails, and it deserves more than a calendar entry.
Provider-side booking UI
Bookings work today, and providers see them. A richer scheduling surface on the provider side is being built.
Billing
Broader billing and settlement flows across the suite, following the same rule as everything else: your line items, your definitions.
Native DICOM & device bridges
Images and reports attach as files today, and the API accepts analyser writes. Native support is a roadmap item, not a shipped one.
What you will not find on this page
We have told you who builds CareSewa and linked the source. What we have not done is pad it out with headshots, a headcount, a funding announcement or a wall of investor logos — not because there is nothing to say, but because you have no way to verify any of it, and most of what goes in that section of a company website exists to look substantial rather than to inform you.
What we will do instead is be specific about the architecture, honest about what is roadmap, upfront about what we do not claim, and available to actual conversation. Judge us on that. It is checkable.
We are also not going to post job openings we have not opened. If you are the kind of engineer, clinician, designer or operator who reads a page like this and finds yourself arguing with it — that is the conversation we want. Write to us. Tell us what we got wrong.
You build things
Engineers and designers who think healthcare software deserved better than it got. Tell us what you would tear down first.
Get in touchYou deliver care
Clinicians and operators who know exactly where this model breaks in the real world. That knowledge is worth more to us than agreement.
Tell us where we are wrongYou run part of the network
A lab, a pharmacy, a fleet, a blood bank. The thesis on this page is only true if you are on the platform.
Become a partnerYou just have questions
About the architecture, the roadmap, the claims, or anything on this page that sounded too good. A real person answers.
Ask usReasonable things to be sceptical about
Including the ones we would ask if we were reading this page rather than writing it.
Because “global” software is usually one market’s assumptions with a currency switcher bolted on. Care in Asia has a specific shape — thousands of small independent participants rather than a few integrated giants — and that shape demands a different architecture, not a different translation file. Building for it first is what makes the platform genuinely multi-country instead of nominally so.
Argue with the thesis. We will bring the product.
The best conversations we have start with someone telling us where this breaks in their world.
Multi-country by design · tenant-isolated · every change audit-logged