Simple, transparent pricing

What counts as an AI fix?

Each exception processed by the StrictLoop agent counts as one fix — whether the outcome is a merged PR, a fallback Issue, or an unresolvable error after the bounded reflexion loop completes.

How does StrictLoop ensure the fix is correct?

Every generated fix is grounded in SEARCH/REPLACE blocks that are validated against the original source AST, then run through a language-appropriate compile check before a PR is opened. Hallucinated diffs that fail compile are discarded and reattempted — never committed.

Is the AI diagnosis loop bounded?

Yes. MAX_REFLEXION_ATTEMPTS = 3 is a hard ceiling. The agent retries diagnosis at most three times, then falls back to a GitHub Issue. No runaway inference — every cycle is auditable and time-boxed.

Is StrictLoop suitable for compliance environments?

Yes. Presidio NER scrubs PII from stack traces before the payload leaves your application. API keys are stored as SHA-256 hashes only — never in plaintext. Every remediation decision writes a timestamped audit trail to MongoDB.

What happens when I hit my quota?

Your application receives an HTTP 402 response from the StrictLoop gateway. No exceptions are silently dropped — they fail loudly so you always know when to upgrade.

Can I upgrade mid-month?

Yes. Upgrading via the dashboard immediately raises your quota. You are billed a prorated amount for the remainder of the billing period.

Is my code sent to third parties?

Only the failing file and its direct dependencies are sent to your configured LLM provider (OpenAI GPT-4o, Anthropic Claude, or a self-hosted Ollama instance). PII is scrubbed client-side by the StrictLoop SDK before the payload leaves your application.