Allston Systems capability statement
Allston Systems builds case-management and digital-service systems the government can keep.
We build on Forge, a software generation platform we license. Forge produces standard .NET, Angular, and USWDS applications with the compliance checks wired into the build: a change that fails an accessibility scan or drifts from a documented control does not merge. The agency owns the source, the generators, the evidence, and the pipelines from the first commit.
Core competencies
- Case management and workflow systems. Records are event-sourced, so every case carries a timestamped decision history. Any case can be viewed exactly as it stood on a given date.
- Public-facing digital services. USWDS shell, Section 508 conformant. Every page is scanned against WCAG 2.1 AA on every commit. A failing scan fails the build.
- Forms and paper-process modernization. An existing PDF or Word form becomes a working accessible multi-step digital form the same day. A person reviews the draft between extraction and generation.
- Legacy system replacement. Old screens are forms and the workflow behind them is a state machine. Migrated records arrive with their history intact.
- Reporting and audit. Cycle times, bottlenecks, and aging cases computed from the event history. FOIA, IG inquiries, and appeals read from the same data.
- Identity. Login.gov or agency IdP sign-in with enforced MFA. Present in the first generated build, not added later.
Differentiators
- The agency owns it from the first commit. Repository, container images, data, generators, evidence. No proprietary runtime. No Allston-hosted service.
- Compliance the system proves about itself. An NIST SP 800-53 control map where each claim cites a passing test. An evidence pack regenerated on every green build in human-readable, machine-readable, and OSCAL forms. An SBOM per release. Signed, digest-pinned images.
- No AI in the delivered system. We use machine learning on our own machines to draft forms from documents. The system the agency operates has no model dependencies and makes no inference calls.
- The exit runbook ships with the first release and is re-tested at every release. It can be verified on a clean machine with no access to us.
- Single tenant by default. One agency, one system, one database, inside the agency’s boundary.
What happens if Allston goes away
Nothing stops. The source, images, data, and runbooks are already the agency’s. A new team follows the exit runbook to build and operate the system, and can keep generating accessible features with the same tools. What ends is our maintenance stream, not the agency’s ability to move. The itemized list: the exit story.
Past performance
Allston Systems was formed in 2026 and has no past performance under its own name. The reference system, a working federal-flavor case system with the USWDS shell, Login.gov sandbox sign-in, and a seeded case scenario, is available for a live session.
The demonstration
One hour, live, on your own material. Bring an intake form, a screenshot of a legacy screen, or nothing. You will watch a working accessible form come out of your document, run a case through its real states, see the audit timeline and the reports fill in, and leave with the exit terms in writing. There is no special demo build.
Company data
| SAM.gov | Registration in progress; UEI and CAGE published once assigned |
| NAICS | 541511, 541512 |
| Size | Small business |
| Platform | Forge, licensed from ThinkForge |
| Contact | Shea Rogers · contact@allstonsystems.com · allstonsystems.com · 6650 Rivers Ave., Suite 100, Charleston, SC 29406 |
Allston Systems LLC · September 2026 · Built to be handed over.
Questions you may already have
Does it have to be multi-tenant? No. Federal systems generate single-tenant by default. One agency, one system, one database.
Is there AI inside the system we would operate? No. We use machine learning on our own machines to draft forms from documents. The delivered system has no model dependencies and makes no inference calls, so AI-inventory questions have a one-word answer.
Is this a low-code platform we would be stuck in? No. Forge emits ordinary .NET and Angular. The feature generators ship with your system, and your team can keep using them without us.
Who hosts it? You do, in your boundary. Delivery is standard containers with Compose and azd artifacts. That is the starting point for GovCloud, agency Kubernetes, and Platform One conversations.
What do you not do? We do not hold a FedRAMP SaaS authorization and we do not offer business-user self-service configuration. We compete on ownership, auditability, and how fast accessible features ship.
What is your relationship to ThinkForge? ThinkForge builds Forge and licenses it to us. Allston Systems is the entity that contracts with agencies, builds on Forge, and hands the result over.