Veteran-owned software engineering, on the ground near NIWC Atlantic

We have engineers on the ground in the Lowcountry who can be at NIWC Atlantic in North Charleston or Joint Base Charleston the same day. For Navy software work, that matters — IPTs, sprint reviews, and program office sidebars are still better in person. We're not running a P.O. box and flying people in from out of state when a sync slips off the calendar.

VooStack is a Service-Disabled Veteran-Owned Small Business, certified through the SBA. That makes us countable toward small business and SDVOSB subcontracting goals on the prime's plan, eligible for SDVOSB set-asides, and a clean teaming partner on SeaPort-NxG and similar vehicles. Primes use us to hit goals without inheriting risk, because we ship working code.

We staff cleared engineers up through Secret as a baseline, with TS/SCI available on specific programs. We work inside customer SCIFs at NIWC Atlantic and Joint Base Charleston, and we keep an unclassified development footprint for the parts of the work that don't need to be behind the fence. Clearance sponsorship details depend on the contract vehicle.

It looks like two-week sprints with a government product owner, written sprint goals tied back to the PWS, demos that produce CDRL evidence, and a backlog that the KO and PM can both read. We don't pretend the FAR doesn't exist. We don't promise velocity we can't bill. And we don't ship to production without an ATO path agreed up front.

Yes, with caveats that most vendors skip. On IL2/IL4 systems we work with the models authorized on Cloud One or the customer's enclave — typically Azure OpenAI in GovCloud or Bedrock Claude where the boundary allows. We design RAG against the actual document repositories in play, build evals before we build features, and write the AI use case memo the ISSM is going to ask for anyway.

We strangle, not rewrite. Existing system stays running while we stand up new services behind an API gateway, route traffic incrementally, and retire legacy modules once the new path has burned in. Typical Navy sustainment systems we see are Java EE on WebLogic, .NET Framework on IIS, or Oracle Forms — all of which have a believable path to containers on Cloud One over 12–24 months.

We sub under SeaPort-NxG, GSA MAS, CIO-SP3 SB, and various agency BPAs through primes. We pursue SDVOSB set-asides directly when the size and scope fit. For rapid starts we also work through OTAs via consortia like Tradewinds and DIU partners. If you have a vehicle and a need, send the PWS — we'll tell you honestly whether we're the right fit.

For uncleared roles, typically 2–4 weeks from signed teaming agreement to badged-and-billing. For cleared roles where the clearance is already in scope, similar. For roles requiring a crossover or new investigation, it's whatever DCSA is doing that quarter — we'll give you a realistic date, not a sales date. We don't bench-warm resumes we can't actually deliver.

Both. Roughly half our work is federal — Navy, Air Force, and civilian agencies — and half is commercial software consulting and AI integration. The commercial work keeps our engineers sharp on modern tooling that federal programs are still catching up to, which is exactly what you want on a modernization or AI integration task order.