Skip to main content
Short answers to the questions people ask most about Octopoda. Each links to the page with the details.
No. Octopoda tests the code you give it, inside its own private sandbox. It never sends requests to your deployed app or your servers. See How Octopoda works.
There is no fixed list: the agent reads your code and, where it can, runs it in the sandbox. It has specific guidance for frameworks and services common in AI-built apps, including Next.js, Django, FastAPI, NestJS, Supabase, Firebase and Auth0. See What Octopoda looks for.
Not necessarily. Octopoda reports only what it can prove, so a clean scan means it found nothing it could reproduce in the time it had. It is strong evidence, not a guarantee.
Most code scans take 10 to 30 minutes, and have a 30-minute limit. Pull request scans have a 20-minute limit. See Scans and results.
No. Octopoda does not train models on your code, and its AI provider, OpenAI, does not either under its API terms. See How Octopoda handles your code.
Yes. The GitHub App reads the repositories you choose, public or private, with read-only access. See GitHub App.
Pull request checks and repository scans from the web app work with GitHub only. The CLI scans any project folder, wherever its code is hosted, and you can run it in any CI system. See Run Octopoda scans in CI.
Scans use credits: 1 for a pull request scan, 5 for a code scan. Plan credits carry over for one more month, then expire. Top-up credits last 12 months. See Plans and credits.
Yes. Your plan stays active until the end of the month you paid for, and you are not charged again. See Manage billing.
Payments are not refundable, except where the law requires it. If a scan fails because of a problem on our side, its credits are refunded automatically.
Yes, on the Team plan, with up to 5 people. See Teams and roles.
Email support@octopoda.dev. Include the scan link or the exact error message if you have one.