Building with login.gov, USWDS, gov.uk Design System, or targeting FedRAMP / StateRAMP? GreatCTO auto-detects the gov-public archetype and ships FedRAMP boundary scoping, NIST 800-53 Rev 5 control mapping, FISMA compliance, Section 508 accessibility, and PIA generation from day one.
login-gov-sdk + uswds or README mentions fedramp / government →Compliance auto-suggested: fedramp · nist-800-53 · fisma · section-508 · pia · ato · cjis · stateramp. Specialist agents activated:
FedRAMP authorization-boundary scoping · NIST 800-53 Rev 5 control mapping (Moderate / High / Tailored) · FISMA · Section 508 / WCAG 2.2 AA · PIA draft · CJIS for law-enforcement integrations · StateRAMP for state-level.
POA&M tracking · ConMon (continuous monitoring) automation · monthly vuln scans · annual assessment prep · NIST 800-53 control evidence collection.
PII change tracking · access logs · retention enforcement · rollback path mandatory · change ticket linked to ATO POA&M.
Validated crypto modules everywhere · MFA flows reviewed · audit log integrity proven · no plaintext fallback paths.
Packs auto-attach when CLI detects pack-specific signals (e.g. twilio in deps → voice-pack). Each pack adds its own reviewer agents + human gates on top of the base archetype pipeline.
7 startups in this space. Click for full pack mapping.
Listed companies operate in this space. Inclusion is based on publicly available product descriptions and does not imply endorsement of or by GreatCTO.
$ npx great-cto init