Datab is built for institutions that need their own infrastructure — not a SaaS rental. The Datab Node sits on the institution's premises, boots its own database, serves its own staff on the LAN, and survives the internet going down.

Who Datab serves today

• Cooperatives — multi-purpose, thrift-and-credit, and producer cooperatives running monthly deduction cycles. DatabStudio Finance is the available sector app.
• Microfinance — same deduction + loan + savings model as cooperatives, with stricter regulatory reporting.

Who Datab plans to serve

• Clinics + primary care — DatabStudio Health (planned).
• Schools — DatabStudio Education (planned).
• SMEs + retail — DatabStudio Retail (planned).
• Public bodies — DatabStudio Government (planned) for sub-national administrative functions where local infrastructure is the regulatory expectation.

What an institution gets

• A Datab Node — the physical or virtualized appliance.
• Pre-installed Datab OS + the DatabStudio sector app for their domain.
• Atlas identity layer, audit log, backup, and the bounded agent previews (Orula + Gu).
• An operator console for institution administrators (datab-os-mobile).
• Member / staff client (DatabStudio Client + datab_mobile member app for cooperatives).

What an institution does NOT get

• Lock-in. Data export is built in; the institution owns its records.
• Cloud dependency. Daily operations don't require an internet connection.
• Hidden telemetry. Audit logs are local; data export to Datab is opt-in.

Institutional pilots are gated. Reach out via Contact.