Workflow · Secure
Security posture audit
A read-only review of what is exposed, what holds secrets and who can reach what, with a fix proposed for every finding.
When to use it
Before a security questionnaire, after a contractor leaves, or when you are not sure what an AI-generated config actually opened.
- Specialists
- 3
- Stages
- 2
- Tier
- Observe
- Duration
- Minutes
Start it with one prompt.
Paste it into Claude Code, Claude Desktop or Cursor once Kapten is connected. Replace the names with yours; Kapten asks for anything it cannot infer.
Connect your agentAudit the security posture of all environments in project “atlas”. Look for public databases, leaked secrets and anything wider than it needs to be.You ask
› Audit the security posture of all environments in project “atlas”. Look for public databases, leaked secrets and anything wider than it needs to be.
Stage 1 · 3 agents in parallel
WardenSecurity review
Network exposure
Public load balancers, open ports, ingress rules and databases reachable from outside the VPC.
WardenSecurity review
Secrets
Secrets in images, environment variables, repository history and logs.
NavigatorArchitecture
Identity and access
Service accounts, IAM roles and who can deploy to which environment.
Stage 2
KaptenOrchestration
Findings with fixes
Ranked by severity, each with the evidence and a proposed plan you can review.
You get
- A severity-ranked findings report
- A proposed remediation plan per finding
- An access map per environment
Related guide
Secrets and configuration for AI-built apps
More workflows
Keep the crew busy.
Ship your first app to production
From a repository that runs on localhost to a production environment in your own cloud account, with a domain, TLS and a rollback.
› Deploy this repo to production on my AWS account in eu-west-3. Use a managed Postgres, put the API behind api.example.com and keep it under 150 €/month.
- Navigator
- Shipwright
- Bosun
- Purser
- Warden
- Kapten
- Helmsman
Production readiness review
Four specialists review an environment in parallel and hand back one prioritised list of what to fix before you rely on it.
› Run a production readiness review on the production environment of project “atlas”. Prioritise what could lose data or take us down.
- Navigator
- Warden
- Lookout
- Purser
- Kapten
Incident triage
When something breaks, start from what changed. The crew correlates the symptom with deployments, config and dependencies, and proposes a mitigation.
› Checkout is returning 502s in production since about 14:10. What changed, and what is the safest way to stop the bleeding?
- Lookout
- Helmsman
- Kapten
Build with Kapten
Start with one service.
Build from there.
Tell us what you want to deploy. We review each request and follow up about fit and onboarding on your preferred cloud.
Free during early access. No card required. Cloud usage billed separately.