PlatformModule 0112 apps
The spine every module runs on At launch
Not a module you open — the layer underneath all __NMOD__. Who can see what, how the system is configured, and a record of everything that ever happened. Foundation first: nothing downstream can be built before identity, roles and the audit trail exist.
Part of Platform & Insight
12 apps in Platform
Identity, Settings & Audit
Users, roles and permissions, company switching, tax and numbering setup — and an immutable record of everything that ever happened.
Industry Packs
What your trade calls things, the stages your work moves through, the extra fields your records need, the documents you issue and the reference data you start with — all of it loaded as a row of configuration, never as a separate version of the software. Pick the pack that matches your trade and the whole system changes its words: the same order screen reads as a job, a matter, a consignment or an appointment, with the same columns underneath. A pack may rename what exists, add fields to tables that exist, and switch discretionary rules off; it may never invent a concept, add a field to a table that does not exist, contain any executable code, or switch off the guarantees — company scoping, the audit trail, money never being a float — because a trade may change its vocabulary and may not opt out of the things the books are trusted for. Adding a trade nobody anticipated is therefore a file somebody writes, not a release somebody ships.
Ask & Print
Ask from your phone, anywhere: a ledger, a bill, today’s packing slips. It comes back as a PDF — or prints on the office printer, with nothing plugged into your phone.
Communications
WhatsApp commands and broadcasts, email and SMS, and the handful of scheduled jobs that carry a nudge to the right person without anyone remembering to send it. Every capability here has more than one interchangeable provider — none of them is ever the source of a figure the business reports.
WhatsApp Command Console
The shop floor does not open a laptop. A worker or a staff member sends a short message — in, out, today’s pieces, leave, an advance — and it becomes a real record: attendance with the time and place it was marked, a production report against the design, a request in the approvals queue. The end-of-day prompt asks what is still open and how long it needs, so tomorrow starts from what is actually pending rather than from memory. Marking attendance checks the phone is at the unit within the radius set for it, with a grace window; a person outside it is not refused, they are flagged for the manager, because a system that locks someone out of being paid for being early at the wrong gate has failed at its job. Every override is recorded with who made it. The words a worker types are in the language they speak, and nothing here ever asks for a password, a bank detail or a document number.
Data Privacy & Consent
What a person’s data may be used for, captured as consent at the point it is given and honoured everywhere downstream — including the right to have it corrected or removed. Retention (how long a record is kept) and deletion (a person’s right to have their own data removed) are two different policies, tracked separately, because a rule that keeps records for the law and a request from a person to be forgotten do not resolve the same way.
Provider Router & Cost Guard
The rule that no capability depends on one outside service, enforced at the moment it matters instead of merely promised. Every capability has an ordered fallback list ending on an option that needs nothing connected, so a courier API that stops answering at 9pm, or an AI key that hits its quota mid-catalogue, drops to the next option instead of stopping the work. A provider that keeps failing is tripped out of the list entirely and retried once after a cooldown rather than hammered; retries inside one provider wait twice as long each time. And every paid call is counted in paise against a ceiling you set — over the ceiling the paid provider is refused, not warned about, and the work completes on a free one. Because every capability is guaranteed a built-in or by-hand option, a spent budget can stop the spending without ever stopping the business.
Payment Data Scope
A written statement of exactly which systems ever see a card or bank credential, and which never do — because every card-capable screen in this system hands that moment to a payment provider’s own secured field and never stores or even passes the number through application code. The statement is what an auditor or a partner asks for before they will connect to this system.
Appearance & Localisation
The two settings a person notices in the first minute and nobody writes a specification for: which time zone a screen shows its dates in, and whether it is drawn light or dark. Time zone is the one that matters for correctness rather than comfort — every timestamp in this system is stored as an absolute moment, so a business working across two zones reads the same event at the right local time in both, and a working day that ends at midnight ends at midnight where the work happened.
Plans & Billing
How Medhava bills the businesses that use it: a free trial, the plan each business is on, the limits that plan sets, and the invoices it receives. Prices are the owner’s to set, and none is shown until they are.
Ask Anywhere
One box on every screen, opened with Ctrl+K: find a record, a screen or a setting by typing its name, or ask the AI a question in plain words. It answers only from records the person asking may see.
Data Import & Migration
Bring an existing business in without retyping it: spreadsheets, exports from desktop accounting software and whole year files, mapped to Medhava’s records and checked before anything is posted. A re-import replaces only what it imported.