Home/About
About

We got tired of
exporting the same student twice.

Omni Forge Software builds the connected software suite for K‑12 districts. Ten applications, one identity, one data core, one governed AI layer — designed together rather than acquired separately and introduced afterwards.

The premise

Districts are not short of software.

A typical district runs a student information system, a walkthrough tool, a review instrument, a tutoring platform, a study product and a reporting layer — six contracts, six logins, six support numbers, and one very tired person in the middle keeping them in agreement with each other.

Every one of those products was a reasonable purchase. The cost is not in any of them. It is in the space between them.

We did not set out to build ten products. We set out to build one platform, and it turned out to have ten faces.
01

Built together, not acquired

Every application shares the same identity, record model and tenancy rules from the first line.

02

Multi‑tenant from the first table

SaaS‑first, many districts on one platform — not a single‑district product retrofitted later.

03

Specification‑led

The core system is written against a published technical specification. Where code and spec disagree, the spec wins.

04

AI as a layer, not a sticker

A shared AI service beside the data core, able to reason across products rather than inside one.

05

Honest about maturity

Some applications have been running for years; some are newer. We will tell you which is which.

How we build

Four commitments we will be held to.

Your data is yours

A district’s records belong to the district. Tenant isolation is enforced at three independent layers, and the API exists so you can get your own data out without asking us.

No walled garden

A documented, district‑scoped REST API with scoped keys and an OpenAPI spec. We would rather you integrate than feel trapped.

AI that shows its work

Every answer names what it read, what it was refused, which model ran and what it cost — and anything actionable waits for a named human to approve it.

Straight answers

On what is mature, what is new, what we do not do, and what a migration will genuinely cost you in staff time. You will find that out eventually anyway.

10Applications
in the suite
1Identity across
all of them
3Layers of tenant
isolation
0Exports required
between apps
Let’s talk

Come and be skeptical at us.

Bring the IT director. Bring the question you think will break it. That conversation is more useful to us than a polite one.