Solutions

Custom software development

When the process is the advantage, configuring somebody else’s product around it is the wrong trade. We build the application, on a foundation that is public so you are never locked to us.

Bending the business to fit the tool

Off-the-shelf software is the right answer for most things. It stops being the right answer at the point where the thing you do differently from your competitors is the thing the product will not let you express.

What we do

Built on the open foundation

Auth, jobs, schemas, rules, tables and charts are the 22 MIT packages on /os. Your application is the part that is yours.

Nothing locked to our infrastructure

Your database, your server, your network. Self-hosted by default.

Presentation separated from logic

Every UI package splits model, controller and design, so the interface can be redrawn later without touching the logic underneath.

Handover as a deliverable

Documentation and a walkthrough, on the assumption that someone else may maintain it.

How an engagement runs

  1. 1
    Scope

    What it must do, and explicitly what it must not.

  2. 2
    Prototype

    The risky part first, not the easy part.

  3. 3
    Build

    In increments you can see and redirect.

  4. 4
    Hand over

    Deployed, documented, and yours.

What it is built on

Assembled from the open-source packages, which you can read before deciding whether to trust what is built on them.

  • @xeplr/auth
  • @xeplr/base-apis
  • @xeplr/db
  • @xeplr/schema-handler
  • @xeplr/ui-table
  • @xeplr/ui-account

See it against your own data

A demo runs on your schema, not a sample dataset. Thirty minutes, no deck.