Veteran-owned software consulting for Tinker-adjacent, FAA, and energy programs
SDVOSB-certified engineers in Central Time. We ship sustainment software, modernize legacy systems, and integrate AI for OKC's defense, aviation, and energy sectors.
OKC programs are stuck between offshore-only consulting and giant primes that won't return calls
Tinker AFB program offices, FAA software vendors, and Anadarko-basin energy operators keep ending up with the same two bad options. Option one: a giant integrator that staffs the contract with whoever's on the bench, charges by the SF-1408, and hands off a Confluence wiki at the end. Option two: an offshore body shop that's cheap on the spreadsheet but produces code your team can't maintain, with timezone gaps that turn a one-day question into a one-week ticket. Meanwhile the actual problem — a 1990s sustainment app, an unmaintained Salesforce instance, a SCADA-to-accounting pipeline held together with Excel — never gets fixed.
- ▸ Depot floor tools running on green-screen AS/400s nobody wants to touch, with mechanics double-entering data into spreadsheets
- ▸ FAA-adjacent software vendors carrying technical debt from a decade of acquisition cycles, blocking new certification work
- ▸ Energy operators with production accounting and field-capture tools built by a contractor who left in 2014
- ▸ Program offices burning ATO timelines waiting on offshore teams 11 hours out of phase with the customer
How we engage with OKC programs and primes
- STEP-01
Mission and constraint review
We start with the actual constraint — IL4/IL5 boundary, ATO timeline, depot floor schedule, FAA certification gates, or production cutover window. Two weeks of interviews with program leads, sysadmins, and the engineers who actually touch the system.
- STEP-02
Architecture and integration map
Document existing GFE, data flows, and integration points: SAP, Maximo, ServiceNow, GCSS-AF, legacy AS/400, mainframe green-screens, SCADA historians. Identify what stays, what wraps, what gets replaced. Written decision record, not a slide deck.
- STEP-03
Incremental delivery in 2-week cycles
Senior engineers on keyboards from week one. Working software every sprint reviewed by your program office. CI/CD into your environment — GitLab, Azure DevOps, or whatever your security boundary allows. No big-bang reveals at month nine.
- STEP-04
Transition to your team
We write the runbooks, train your government civilians or contractor staff, and hand off with documentation that survives turnover. Optional sustainment retainer for the first 6-12 months while your team takes the wheel.
# Example: wrapping a legacy depot work-order API behind a modern
# FastAPI service so downstream tools (mobile, dashboards, RAG agents)
# can consume it without touching the AS/400 directly.
from fastapi import FastAPI, HTTPException, Depends
from pydantic import BaseModel
from typing import Optional
import httpx, os
app = FastAPI(title="depot-workorder-gateway")
LEGACY_URL = os.environ["LEGACY_AS400_BRIDGE"] # internal only
TIMEOUT = httpx.Timeout(10.0, connect=3.0)
class WorkOrder(BaseModel):
wo_id: str
aircraft_tail: str
status: str
nsn: Optional[str] = None
opened_utc: str
async def auth(token: str):
# PIV/CAC-backed JWT validation happens upstream at the mesh edge
if not token:
raise HTTPException(401, "missing token")
@app.get("/workorders/{wo_id}", response_model=WorkOrder)
async def get_wo(wo_id: str, _=Depends(auth)):
async with httpx.AsyncClient(timeout=TIMEOUT) as c:
r = await c.get(f"{LEGACY_URL}/wo/{wo_id}")
if r.status_code == 404:
raise HTTPException(404, "work order not found")
r.raise_for_status()
raw = r.json()
return WorkOrder(
wo_id=raw["WONUM"].strip(),
aircraft_tail=raw["TAILNO"].strip(),
status=raw["STAT"].strip(),
nsn=raw.get("NSN", "").strip() or None,
opened_utc=raw["OPNDT"],
)Strangler-pattern gateway in front of a legacy depot work-order system. Lets new tools (mobile, BI, RAG) integrate without rewriting the AS/400.
Field FAQ.
→ Are you actually based in Oklahoma City, or is this a sales front?
We have engineering presence on the ground in the OKC metro and operate in Central Time alongside clients at Tinker, the Mike Monroney Aeronautical Center, and the energy corridor. We're a US-based, veteran-owned firm — not a reseller fronting offshore delivery. When a program office needs someone in the room for a critical design review or a depot floor walk, that happens. We're not flying in from a coast for every meeting.
→ Can you support SDVOSB set-asides for Tinker AFB or FAA work?
Yes. We are SDVOSB-certified through the SBA Veteran Small Business Certification (VetCert) program and registered in SAM.gov with the relevant NAICS codes for custom software (541511), computer systems design (541512), and IT consulting. We can prime small-business and SDVOSB set-asides directly, or team as a sub on larger vehicles. We've been through the paperwork — DUNS/UEI, CAGE, reps and certs — and won't slow your acquisition timeline learning it.
→ What kind of work do you typically do for depot sustainment programs?
Common patterns: wrapping legacy work-order or supply systems behind modern APIs so mobile and analytics tools can consume them; building scheduling and parts-tracking tools that integrate with GCSS-AF, Maximo, or SAP; modernizing green-screen mainframe workflows that mechanics and planners actually use daily; and AI-assisted technical-data search across thousands of pages of T.O.s and engineering drawings. We focus on tools that survive the next program manager rotation.
→ Do your engineers hold security clearances?
We staff cleared engineers (Secret and TS, with some SCI eligibility) for programs that require them, and we have a process for sponsoring clearances when a contract justifies it. For unclassified work that still requires CUI handling, we operate inside CMMC-aligned controls. Clearance staffing is project-dependent — tell us the requirement and we'll tell you honestly whether we can staff it on your timeline or need to team.
→ We're an energy operator with aging field tooling. Can you help?
Yes. A lot of OKC and broader Anadarko-basin operators are running production accounting, lease management, and field-data-capture tools that were custom-built 15-20 years ago on tech stacks no one wants to maintain. We modernize those — typically by extracting the core data model, putting a modern API and web/mobile UI on top, and integrating with current SCADA historians and accounting systems like Quorum or P2. Incremental migration, not rip-and-replace.
→ How do you integrate AI without it becoming a science project?
We treat LLMs as a component, not a product. Concrete pattern: retrieval-augmented generation over your actual documents (T.O.s, SOPs, contracts, ticket history) with citation-backed answers, deployed behind your auth boundary using Claude or GPT via API, or a self-hosted model when data residency requires it. We measure precision on a real eval set before anything ships to users. If it doesn't beat the existing search bar, we don't ship it.
→ What does staff augmentation look like with VooStack?
Senior engineers — typically 10+ years, US-based, in Central Time — embedded with your team for 3 to 12 month engagements. They show up in your standups, your repo, your Jira, and write code that your team will own after. We don't send junior bench staff and we don't pad teams. Rates are higher than offshore body shops and lower than the big consulting firms; the value is throughput per engineer.
→ How fast can you start?
For staff augmentation with uncleared work, typically 2-3 weeks from signed SOW to engineers on keyboards. For cleared work, it depends on facility sponsorship and clearance verification — usually 4-8 weeks. For a full project engagement with discovery, expect a 2-week scoping sprint followed by a fixed-scope or T&M proposal. We don't quote 'next quarter' start dates to win deals we can't actually staff.
→ Do you only work with federal clients?
No. Roughly half our work is commercial — energy operators, insurance carriers, healthcare networks, and mid-market SaaS companies, many in the OKC/Tulsa/DFW corridor. The federal discipline (documentation, security, traceability) tends to make our commercial delivery sharper, and the commercial pace keeps our federal work from drifting into pure compliance theater. Same engineers across both sides of the house.
Continue recon.
Services overview
Custom development, modernization, AI integration, and staff augmentation.
REL-02Case studies
Shipped work across federal sustainment, energy operations, and commercial platforms.
REL-03Engagement packages
Fixed-scope discovery, modernization sprints, and embedded engineering retainers.
REL-04Talk to us
Reach a senior engineer directly — no SDR gauntlet, no discovery-call theater.
Ready to talk to engineers who've shipped on Tinker-adjacent and FAA programs? Get in touch.
Talk to a VooStack operator. We respond within one business day.