Capabilities statement
What we build, how we build it, and what we can be tasked with
Figures as of 2026-11-09
Why team with us
What a contracting officer or a prime gets from us.
Veteran-owned
SBA-certified SDVOSB and HUBZone small business, led by a service-disabled veteran.
A complete kit
Identity, security headers, consent, forms, mail, theming, and testing as shared packages published from one platform repository, plus one automated delivery pipeline. A contract starts with a working system, not a blank repository.
Proof, not promises
Every code change we make leaves a trail: the ticket, the reasoning, the checks, the deploy. We would rather show you the repository than a slide. What git does not record is listed under Known limits on this page.
Registration and credentials
Everything a contracting officer needs to qualify us for a set-aside opportunity, without a phone call.
Registration details
Point of contact
John Roller, President
NAICS codes
- 541512Computer Systems Design Services
- 541519Other Computer Related Services
- 541330Engineering Services
- 541990All Other Professional, Scientific, and Technical Services
Download the capabilities statement (PDF, opens in a new tab)
Platform architecture, engineering methodology, how we work, and our security, identity, and secrets posture are on How we work, where a technical reviewer looks.
Company overview
Turbo Client Systems (TCS) builds zero-trust, zero-knowledge, Azure-native tools for commercial companies, federal contractors, and federal agencies. The tools sign people in with Microsoft Entra ID and keep customer data in the customer’s own Microsoft 365 tenant. Four people run 29 active repositories across three GitHub organizations split by circle of trust (the tools we sell, the shared services, and the marketing sites), one Entra tenant, and one continuous-integration standard.
What we hold about a customer is billing: who pays us for which tools, and nothing beyond what Stripe, our payment processor, holds. The tools run no analytics. We hold what a person chooses to send us (a bug report, a message or booking through a site, or written consent to be named in a case study) and nothing else about their use of a tool.
TCS is pre-revenue and pre-contract. The known-limits section below states what is not in place yet.
Core competencies
Each capability below is backed by something already built and running, and readable in one of our repositories.
| Competency | What we can be tasked with | Evidence already built |
|---|---|---|
| Full-stack web application delivery | Next.js 16, React 19, and TypeScript 7 applications with Tailwind 4, shared component libraries, translation, and consent gating | 3 public sites and 4 web tools on our own domains; 46 shared packages in one platform repository |
| Microsoft identity and Graph engineering | Entra ID sign-in in the browser, delegated Microsoft Graph access, a short-lived elevated sign-in for admin-only actions, SharePoint site and list provisioning, and endpoint tables for the commercial, GCC High, and DoD clouds | The sign-in package every web tool uses; the Portal, which provisions a SharePoint site in the customer’s tenant |
| Customer-owned data architecture | Applications that keep customer data in the customer’s own Microsoft 365 tenant, with access decided by the customer’s Entra groups | Governance and the Portal |
| GRC and compliance content engineering | A linked graph of statutes, standards, mandates, roles, workflows, exams, and policy templates | Our governance registry, with exams for CMMC Level 2, DFARS CUI protection, NIST CSF 2.0, FISMA, ISO/IEC 27001, HIPAA, HITECH, SOX 404, CCPA, and CFAA |
| Federal data tooling | Daily collection of public federal opportunity and award data | The Turbo Bid System, which reads SAM.gov Opportunities, Grants.gov, and USAspending each day |
| Native Windows diagnostics | Tauri 2 and Rust desktop applications that read Windows event logs and system state, with an in-app updater | The Turbo Telemetry System desktop app, version 2.1.29 |
| Cybersecurity and compliance tooling | Tools that support CMMC, NIST, and ISO 27001 work by recording evidence and settings in the customer’s tenant; they certify no one | Governance records attestations with evidence in the customer’s SharePoint site; Config and Drift read tenant settings against Microsoft’s recommendation |
| Data analytics and reporting | Reports and views over compliance evidence and system event data | WinDEETS lets a user flag and export Windows events; Drift records a snapshot of tenant settings each day so two days can be compared |
| IT modernization | Rebuilding a system’s foundation when the rebuild is the better call; we have no federal modernization contract yet | We moved the Windows event-monitoring app from Electron to Rust and Tauri although Electron already worked (About page) |
| Architecture and compliance consulting | Architecture and compliance strategy advice from the engineers who build the product | The dated work samples on the How we work page, each linked to the code and the checks behind it |
| Delivery governance and CI/CD | Reusable GitHub Actions workflows, a seven-check required gate, merge queues, credential scanning, private package publishing with Changesets, and Dependabot; the same checks applied to a customer’s infrastructure as code and deployment pipelines | Every site and tool repository calls the same shared workflow |
Products and past performance
We have no contract past performance yet: TCS is pre-contract. These are our own products, from the Portal’s catalog, grouped by the job they do. Rollback’s undo is not built yet. A prime should read this section as what we have built, not as references.
| Product | Where | Job | What it does |
|---|---|---|---|
| Turbo Access System | access.turboclientsystems.com (opens in a new tab) | Access | Creates, changes and removes access for people, licenses and groups, with the tenant admin signed in as themselves. |
| Turbo Identity System | identity.turboclientsystems.com (opens in a new tab) | Access | |
| Turbo Workspace System | workspace.turboclientsystems.com (opens in a new tab) | Access | Shows orphan sites, sharing and group expiration through Microsoft Graph under your sign-in, and changes sharing settings, group expiration and one group’s owners. |
| Turbo Config System | config.turboclientsystems.com (opens in a new tab) | Change | Reads five tenant settings against Microsoft’s recommendation and changes one through a guarded button after an approver approves. |
| Turbo Drift System | drift.turboclientsystems.com (opens in a new tab) | Change | A Logic App in your own Azure subscription reads the tenant’s settings once a day, compares them to the day before and records each snapshot on your SharePoint site. |
| Turbo Rollback System | rollback.turboclientsystems.com (opens in a new tab) | Change | |
| Turbo Device System | device.turboclientsystems.com (opens in a new tab) | Devices | Shows how Intune policies, enrollment, apps and update rings are set, and can assign them to a group after an approver in the tenant approves. |
| Turbo Email System | email.turboclientsystems.com (opens in a new tab) | Devices | Lists your domains, the DNS records Microsoft expects and the published SPF, DKIM and DMARC, read through your own Azure Automation account. |
| Turbo Telemetry System (desktop) | windeets.com (opens in a new tab) | Devices | A Windows desktop app that reads a PC’s event logs and inventory when you open a page, under your Windows account, with no sign-in. It keeps only the events you flag. |
| Turbo Data System | data.turboclientsystems.com (opens in a new tab) | Compliance | Lists sensitivity labels, retention labels and eDiscovery cases with their holds and searches, and can request a hold or a search that a second approver must approve. |
| Turbo Governance System | governance.turboclientsystems.com (opens in a new tab) | Compliance | Maps statutes and standards into one graph, runs staff exams in the browser and records attestations, with the evidence kept in your SharePoint site. |
| Turbo Training System | training.turboclientsystems.com (opens in a new tab) | Compliance | Shows who is eligible for a training role, and a Training administrator saves exams and tests to a list in your tenant. |
| Turbo Cloud System | cloud.turboclientsystems.com (opens in a new tab) | Cloud | Shows Azure spend, role assignments, policy and automations, and acts on resources through your own Azure roles. |
| Turbo Incident System | incident.turboclientsystems.com (opens in a new tab) | Cloud | Shows the Defender incident queue, read through Microsoft Graph with the admin’s own token. |
| Turbo Bid System | bid.turboclientsystems.com (opens in a new tab) | Federal | Reads a public feed of federal notices and awards and grades each opportunity A to F against your past performance. |
| Turbo AI System | ai.turboclientsystems.com (opens in a new tab) | AI, media | |
| Turbo Media System | media.turboclientsystems.com (opens in a new tab) | AI, media | |
| Turbo Portal System | portal.turboclientsystems.com (opens in a new tab) | Onboarding | Customer tenant onboarding; provisions the workspace-map SharePoint site; products register by manifest |
Azure migration readiness
Already in Microsoft. Identity (Entra ID), authorization (Entra groups), customer data and our own configuration model (SharePoint in the customer’s tenant), and site mail (Exchange Online). The Microsoft endpoint package already carries typed tables for the commercial, GCC High, and DoD clouds. We have not deployed to GCC High or DoD, and would prove it in a test tenant before relying on it.
Outside Microsoft today. Hosting is on Vercel (with Vercel BotID, Vercel Web Analytics, which measures a visit only after the visitor consents, and Vercel Blob storage for the Turbo Bid System’s feed). Source, CI, and packages are on GitHub, and CI runs on self-hosted runners on our own machines. Moving to Azure means replacing these.
Known limits
We are pre-revenue and pre-contract. These are the limits a prime should price rather than discover.
- Hosting is Vercel’s commercial service, not Azure.
- Not everything is in the trail. Changes to Azure, GitHub settings and Vercel are not in the git ledger. Every code change leaves a ticket, a pull request and its checks; a change to a live setting does not, and a person makes it.
- A person promotes every release. Production changes only when a person merges the release pull request into main. That is a control, because no code reaches customers unreviewed by a decision, and a limit, because a fix waits for that click.
- Our Content Security Policy allows inline script: `script-src` is `'self' 'unsafe-inline'` plus the Vercel Analytics host, so a script injected as inline text would run. A hash cannot cover the per-build chunk list or each page’s payload, and a nonce needs every page rendered on each request, which rules out static pages and CDN caching.
- Keys remain (eight in the organization secret store for CI, four that applications read at runtime), and they are rotated by hand.
- Each repository pulls the shared rules with one command, run by hand; nothing pulls them on a schedule.
- CI runs on self-hosted runners on our own machines.
- Unit tests (Vitest) are a required check. The browser accessibility check (Playwright with axe) runs as a separate E2E check in each of our six site repositories, and it is not one of the seven required checks.
- GitHub’s paid secret-scanning add-on is not purchased; Gitleaks in CI stands in.
- Governance’s audit trail is not append-only yet: a person can still edit or delete their own entries.
- The company is four people.
Differentiators
- Customer data stays in the customer’s tenant. Governance keeps answers and evidence in the customer’s own Microsoft 365 tenant, reached with the signed-in person’s delegated token, and lint rules forbid the server code paths that would let it receive them.
- One platform, one standard. Identity, consent, security headers, forms, mail, theming, translation, testing presets, and lint rules are versioned packages that every application consumes. A fix ships once and reaches every application through Dependabot.
- Compliance content is our product domain. We maintain a linked graph of statutes, standards, mandates, roles, workflows, and exams, including CMMC Level 2, DFARS CUI protection, NIST CSF 2.0, FISMA, ISO/IEC 27001, HIPAA, HITECH, SOX 404, and CCPA.
How we work with a prime. Everything we build is TypeScript on Next.js with Microsoft Entra sign-in, so a prime’s own engineers can maintain it.
Company data
- Legal name
- Turbo Client Systems, Inc.
- Location
- Merritt Island, FL
- UEI
- CPYJP28MFBF8
- CAGE code
- 9XZ43
- Socioeconomic status
- Service-Disabled Veteran-Owned Small Business (SDVOSB); HUBZone certified
- Security clearances
- Active clearances held by team members (confirmed 2026-08-04)
- Point of contact
- John Roller, President
- Phone
- 321-376-7160
| Code | Description |
|---|---|
| 541512 | Computer Systems Design Services |
| 541519 | Other Computer Related Services |
| 541330 | Engineering Services |
| 541990 | All Other Professional, Scientific, and Technical Services |
