Government software development for state, local and education agencies
Custom applications, websites, portals and accessibility remediation for public agencies. Delivered in fixed phases, documented and built to WCAG 2.1 AA.
Last updated October 18, 2026
Software projects agencies can buy and finish
Many agency software needs are small and specific: a resident-facing form, a permit tracker, a website that finally meets accessibility rules. These projects stall because they are too small for large integrators.
Konnex takes them on. We scope tightly, price each phase and build with a hybrid team. You get code you own, documentation and a handover.
Our founder builds production software in React, TypeScript and Supabase, and stays involved in technical decisions.
What we build
Public content and non-production work suit our hybrid model best.
Websites and portals
Builds, redesigns and migrations for public-facing sites, including hosting in US regions.
Accessibility remediation
WCAG 2.1 AA audits and fixes for websites, documents and web apps.
Custom applications
Forms, case tracking, scheduling and workflow tools for internal teams and residents.
Modernization in phases
Replace legacy screens and spreadsheets step by step, without a risky big-bang cutover.
Data and integrations
APIs, data pipelines, dashboards and reporting on public or de-identified data.
QA and test automation
Test plans, regression suites and automation against test environments.
ADA Title II: the deadline is real
The US Department of Justice requires state and local government websites and apps to meet WCAG 2.1 AA. An interim final rule in April 2026 set the dates below.
| Public entity | Compliance date |
|---|---|
| Serving 50,000 or more people | April 26, 2027 |
| Serving fewer than 50,000 people, and special districts | April 26, 2028 |
Source: US DOJ interim final rule, Apr 20, 2026, via Reed Smith.
Remediation of public pages is a strong fit for our model: the content is public, the work is well defined and it scales with a team.
How a project runs
- Scope. A short discovery to agree deliverables, acceptance criteria and data rules.
- Fixed phases. Work is split into phases with a price and a deliverable each.
- Build and test. Code and synthetic test data only. Agency data stays in US-hosted environments.
- Accept and hand over. You review, accept and get the code, documentation and training.
For schools and colleges
K-12 districts and public colleges have their own rules on student data.
K-12 districts
District websites, accessibility fixes, staff-facing tools and reporting on de-identified data. Student records stay under district control, as FERPA and your data agreements require.
Public colleges
Department sites, internal workflow tools, integrations and QA capacity for campus IT teams.
Common questions
For IT directors, CIO offices and procurement. Still unsure? Ask us directly.
Can a government agency hire an offshore software team?
Often yes, for work that does not touch restricted data, such as public websites, code built on synthetic data and testing. Some states and data types require US-only work. Read our guide.
Do you build to Section 508 and WCAG 2.1 AA?
Yes. Accessibility is part of our definition of done, and we test with automated tools and manual keyboard and screen reader checks.
Who owns the code?
You do. Code, documentation and design files are handed over at acceptance.
What stack do you use?
We work in your stack where one exists. For new builds we often use React and TypeScript with a US-region cloud host.
How do you price projects?
Fixed price per phase, after a short scoping step. That keeps many projects under small-purchase thresholds.
Before you buy
The 3 pages procurement teams ask for most.
Have a project in mind?
Send the scope, the timeline and your budget range. We reply with questions, a delivery plan and the purchasing route that fits.