SOPHIA XT
ERP · Enterprise business suites

An ERP that refuses an unbalanced journal.

We write enterprise business suites for companies that have outgrown a spreadsheet and a general-purpose CRM. One system holds sales, purchasing, the books and the reporting over all of it, and the ledger underneath will not let them disagree.

See it running
(586) 300-4975
Search or run a command
post
⌘K
Post invoice INV-1042
⌘P
New purchase order
⌘O
Run trial balance
⌘T
Post vendor bill
⌘B
Add customer
⌘C
Ledger
now
Journal posted and balanced
Debits 4,280.00 equal credits 4,280.00. The journal is
frozen.
Open journal
Dismiss
Ledger
Receivables
Payables
Receivables, last 8 weeks
$38.4k
$29.3k
$38.4k
Trial balance ties out
An illustration of the posting flow, not a customer's books.
What it does

The whole operation, posting to one ledger.

The parts below are running in production today. Each new build starts from the engines already proven correct and writes the rest around how your company actually works.

  1. A real double-entry ledger

    Unbalanced journals are refused, posted journals are frozen, and a reversal mirrors the original instead of editing history. The trial balance proves debits equal credits.

  2. Order to cash

    Quotations, orders, invoices and receivables, closed end to end and posting through the ledger.

  3. Procure to pay

    Vendors, purchase orders, bills, debit memos and vendor returns on the same books.

  4. Tenancy built into the data layer

    Every query is scoped to the company that owns it. A read across companies returns nothing, and a red-team pass hunting for exactly that came back clean.

  5. An assistant that cites the row

    Answers come from your live records and return the identifier behind each claim, so every answer can be checked or fails loudly.

  6. Imports that survive real files

    Spreadsheets and exports are staged, sorted into ready, warned, failed and duplicate, and committed in one transaction after review.

In production

Running for customers today. Open it.

The public Ethereal EBS site

Ethereal EBS

A multi-tenant enterprise business suite with a real double-entry ledger underneath it and a cross-company wholesale market wired in.

  • A platform kernel that treats tenancy as a primitive rather than a filter applied later: every repository call is scoped, and a cross-tenant read returns a 404 rather than a row.
  • A double-entry general ledger that refuses an unbalanced journal, freezes a journal once posted, mirrors a reversal instead of editing history, and proves debits equal credits on the trial balance.
  • Order-to-cash and procure-to-pay closed end to end: quotations, orders, invoices and receivables on one side; vendors, purchase orders, bills, debit memos and vendor returns on the other, all posting through the ledger.
The public Tophat site

Tophat

An enterprise business suite for a commercial real estate brokerage, with an assistant that answers from the brokerage's own rows and cites the record it read.

  • Clients, properties, listings, projects, proposals and documents in one system, with a rent roll, comparables and the reporting over all of it.
  • A request workflow that enforces order: a step that depends on the exclusive listing agreement refuses to be marked done by name until the agreement is done, and a step declaring a required link or file refuses to complete without one.
  • An assistant in command mode that answers from live rows and returns the record identifier behind each claim, so an answer can be resolved back to the row or fail loudly as not found.
How a build runs

Four steps, and you can watch every one.

Step 1

Map how the work moves

We start from how your people do the job today, and write down the rules the software has to enforce.

Step 2

Build the records first

Customers, stock, jobs and the books come before screens, with the rules in the data layer where they cannot be skipped.

Step 3

Bring your data across

Existing spreadsheets and exports come in through a staged import you review before anything is committed.

Step 4

Deploy where you want it

Your own hardware, a host you already pay for, or a server you control. You keep the keys.

Questions

What people ask first.

No. The system is written for your operation. What carries over between builds are the engines already proven correct, such as the ledger, receivables, payables and tenant isolation, so you are not paying to rediscover how double-entry works.

Tell us what you run on now.

A call is enough to know whether a custom system is worth it for you, or whether what you have should stay.

Also builtPoint of sale softwareThree stores, one system, and every count stays its own.Read it Also builtDispatch softwareFrom the call to the closed job, entered once.Read it