Complete your subscription setup
Verifying your AWS Marketplace subscription token...
After verification, continue to sign in and complete organization onboarding.
Deploy governed agents across operations, finance, risk, customer service, IT, and engineering with policy controls, approvals, and audit-ready receipts.
Autonomy is staged, policy-bound, and auditable. Critical actions stay behind explicit controls, approvals, and accountability.
Verifying your AWS Marketplace subscription token...
After verification, continue to sign in and complete organization onboarding.
Six checkpoints keep enterprise agent execution constrained, inspectable, and accountable.
Define business scope, systems, risk tier, and operating constraints before any execution.
Preview expected impact, risk, effort, and cost with explicit assumptions.
Execution stays behind explicit human and policy checkpoints, captured in receipts.
Agents execute across approved workflows with policy guardrails and full action capture.
Exceptions, high-risk actions, and policy conflicts route to the right decision owner.
Outcomes, evidence, and accountability records are finalized for operational and compliance review.
Every run produces a timeline you can audit: what happened, when it happened, and why it was allowed.
A single view from intake to execution to outcomes, with all control checkpoints preserved.
Inspect tools used and outputs produced, tied to the run.
Every governed decision maps to actions, owners, timestamps, and final outcomes.
Policy, risk, and budget constraints are enforced before and during runs; hard stops prevent drift.
Coordinate agent operations across business, risk, customer, and technical domains.
Execution stays inside policy boundaries with explicit approvals and ownership controls.
Receipts capture decisions, actions, tool calls, evidence, and outcomes.
Enterprise AI transformation service across agents, sensors, automations, and policy controls. CodeOps is one execution module inside this operating model.
Role separation, explicit approvals, and policy checkpoints are designed before scale.
From event detection to action routing and completion, flows run with full traceability.
Every critical action is tied to receipts, timelines, and enforceable decision gates.
Prebuilt transformation bundles by industry, each combining workflow agents, live sensors, and governed automations.
KYC/AML triage, risk checks, anomaly sensors, and escalation automation for compliant operations.
Authorization workflows, intake operations, PHI-aware controls, and compliance evidence generation.
IoT-driven maintenance intelligence, quality incident routing, and supply exception automation.
Service coordination agents, safety/utility sensors, and cross-department escalation rails.
Structured delivery from initial governance setup to managed enterprise-scale operations.
4-6 weeks
8-12 weeks
12-month engagement
Built with enterprise controls in mind and explicit scope boundaries.
Change management, approval checkpoints, least privilege, and audit trails are built into the workflow.
Payment data is handled by PCI-compliant processors; Scatman minimizes PCI scope and does not store raw card data.
Receipts, logs, diffs, and policy decisions are timestamped and exportable for reviews.
Governed AI products for engineering teams and enterprise operations.
AI-governed code generation pipeline. Submit a task, get a PR with full audit trail — intake, estimate, build, review, and merge with policy controls at every step.
Full enterprise AI governance platform. Deploy governed agents across departments with policy controls, approval workflows, and audit-ready operations.
Updated March 2026 for the enterprise transformation rollout.
Core questions on governance controls, autonomy levels, receipts, and enterprise rollout.
No. Engineering is one execution surface. Scatman Governance Core supports operations, finance, risk, customer, IT, and engineering workflows.
Yes, but only in approved low-risk lanes. Most enterprises start with human approvals, then increase autonomy per workflow after controls and quality thresholds are proven.
Receipts are auditable governance records: intake, estimate, approvals, policy decisions, tool calls, artifacts, and final outcomes with timestamps.
Scatman is built with SOC 2-aligned controls and clear PCI scope boundaries. For payments, card data is processed by PCI-compliant providers. Contact us for current attestation and documentation status.
Execution is blocked or escalated based on policy. The violation, owner handoff, and remediation actions are captured in the same receipt trail.
Tell us your first department use case and transformation goals. We'll reply with sector-fit workflow options and rollout steps.
Create a work order to see delivery status here.
Pull deliverable status, preflight results, and receipt timeline for any runId.
Review estimate history and acceptance status.
Loading repositories...
Manage your plan, usage, and payment settings.
$0/month
Add a payment method to enable paid features.
Every billable AI action consumes credits at usage cost + 20% margin.
Payment activation is manual during beta. Contact us to enable paid features and set up billing.
No invoices yet.
Everything you need to know about using Scatman.
Only repos you add can be used for code deliveries.
Scatman creates a plan, shows you an estimate, waits for your approval, generates a PR, reviews it, and only merges when you explicitly approve.
Your monthly credits are shown as a percentage. Credits are 95% of your monthly plan price (for example: $20 plan → $19 credits).
Every billable AI action is charged from monthly credits. Charges are based on AI usage cost plus a 20% margin for compute and platform overhead.
Estimate generation, acceptance, run execution, review, and promotion all consume credits while your run progresses.
Common reasons:
repo_not_accessibleThe repository isn't connected or Scatman doesn't have access.
Fix: Go to Settings → Connected Repos and add the repository.
diff_invalid / patch_failedThe generated code changes couldn't be applied cleanly.
Try:
timeoutThe operation took too long, usually on very large repositories.
Try: Start with smaller, simpler changes to warm the cache.
Scatman never merges without your explicit approval.
Every PR is created as a draft, reviewed by our AI reviewer, and only merged when you click "Merge PR" in the run view. You always have final control over what goes into your codebase.
Still have questions?
We're here to help. Send us a message and we'll get back to you.
Or email us directly:
support@scatman.aiLast updated: February 2026
By accessing or using Scatman ("the Service"), you agree to be bound by these Terms of Service. If you disagree with any part of these terms, you may not access the Service.
Scatman provides AI-powered code generation and delivery services. The Service creates pull requests on your behalf based on your instructions and does not merge code without your explicit approval.
Usage is billed according to our pricing policy. Free tier includes $10/month of usage. Additional usage requires payment activation. You agree to pay all fees associated with your use of the Service.
Code generated by the Service is owned by you. Scatman retains no rights to code created for your repositories. The Service itself, including its AI models and infrastructure, remains the property of Scatman.
Scatman is provided "as is" without warranty. We are not liable for any damages arising from the use of generated code. You are responsible for testing and validating all code before deployment to production.
For questions about these Terms, contact us at legal@scatman.ai
Last updated: February 2026
Code content is processed transiently and not stored after delivery. Account and billing data is retained while your account is active. You may request deletion at any time.
We use:
For privacy-related inquiries, contact us at privacy@scatman.ai
How we protect your code and data.
OAuth 2.0 with GitHub. JWT tokens with short expiration. No passwords stored.
Hosted on AWS with VPC isolation. All services run in private subnets. Regular security patches.
Code is fetched, processed by AI, and delivered as a PR. Not persisted after delivery.
Stripe handles all payment processing. We never see or store your card details.
Found a security issue?
security@scatman.aiLast updated: February 2026
Beta Period Notice
During the beta period, all refund requests are reviewed manually. We're committed to making things right.
Approved refunds are credited to your original payment method. Processing time depends on your bank (typically 5-10 business days).
Questions about refunds?
billing@scatman.ai