Solutions · Enterprise systems

Operations software, built for one organisation and run with it.

Portals, inventory, approvals and multi-tenant platforms for organisations whose process does not fit a packaged product, engineered to the same rules as our infrastructure work.

  • Operations portals
  • Inventory
  • Multi-tenant platforms
  • Agent access
01Decisions

The decisions the system carries.

Enterprise software fails quietly: a spreadsheet nobody trusts, an approval given in a chat thread, a report rebuilt by hand each month. We replace those with systems of record.

  1. 01

    Who may approve, release or see a record

  2. 02

    What left the store, and who signed for it

  3. 03

    Which projects and reports are waiting on whom

  4. 04

    What an AI assistant is allowed to touch

02Workflows

The workflows it runs.

  1. 01Projects, documents and approval workflows with role-based access
  2. 02Scan-to-dispatch inventory against approved quantities, with two-level approval
  3. 03Monthly reporting exported in the organisation's own template
  4. 04Isolated workspaces per institution on one multi-tenant platform
  5. 05Tasks, projects and notes opened to AI agents through scoped, revocable tokens
03How we engage

Two kinds of work, one engineering standard.

We keep a clear line between what we own and what we build for others. Products such as ClearMind are designed, built and operated by MeerTech. Client systems are built for an organisation that owns and runs them, and we say which is which on every entry in the portfolio.

Both are held to the same rules: offline first where the field demands it, double entry wherever money or stock moves, an audit trail on every change, and no invented numbers. The stack is deliberately plain: Python and FastAPI, PostgreSQL, React, and containers behind a reverse proxy.

Equipment racks strung with patch cables and status lights in a dark hall

Operating conditions

Two people are involved in every release of stock. The system enforces that line instead of relying on policy.

04What we have built

Shipped, and stated by status.

Internal client systems have no public address. We describe them here and demonstrate them on a call.

  • Remote Portal

    Deployed

    An internal operations portal for a mini-grid developer covering projects, documents, approvals and team chat, with site progress reports that produce a PowerPoint in the company's own template.

  • MSIV

    Deployed

    Multi-store inventory for a mini-grid developer: barcode scanning on rugged handhelds, Bluetooth label printing, approvals, dispatch, purchase orders and returns, working offline where there is no signal.

    Read more
  • Career services platform

    Deployed

    A multi-tenant career services system for Nigerian tertiary institutions: student assessments, counsellor case queues, and tracking of industrial training and national service placements.

  • ClearMind

    Deployed

    Tasks, projects, notes, habits and goals in one workspace that works offline, with an AI assistant and an MCP server so agents such as Claude can act on your data through scoped OAuth access.

    Read more
05Governance

The lines we do not cross.

  1. 01

    Deny by default

    Access is refused unless explicitly granted, enforced at the row in the database.

  2. 02

    Append-only history

    Every change leaves a trail. Corrections are new entries that reference what they correct.

  3. 03

    Internal stays internal

    We do not publish client URLs, login pages, hosts or data, on this site or anywhere else.

Contact

Tell us what you are trying to operate.

Describe the infrastructure, the workflow that costs you most, and your connectivity as it really is. The first call is with an engineer.