> ## Documentation Index
> Fetch the complete documentation index at: https://docs.octopoda.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Octopoda frequently asked questions

> Answers to common questions about Octopoda: what it scans, how long scans take, what a clean scan means, AI training, credits, refunds and GitHub support.

Short answers to the questions people ask most about Octopoda. Each links to the page with the details.

> [accordion] Does Octopoda test my live website?
>
> 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](https://docs.octopoda.dev/how-it-works.md).

> [accordion] Which languages and frameworks does it support?
>
> 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](https://docs.octopoda.dev/how-it-works.md#what-octopoda-looks-for).

> [accordion] If a scan finds nothing, is my app secure?
>
> 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.

> [accordion] How long does a scan take?
>
> 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](https://docs.octopoda.dev/scanning/scan-results.md).

> [accordion] Is my code used to train AI models?
>
> 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](https://docs.octopoda.dev/security/your-code.md).

> [accordion] Do you scan private repositories?
>
> Yes. The GitHub App reads the repositories you choose, public or private, with read-only access. See [GitHub App](https://docs.octopoda.dev/integrations/github-app.md).

> [accordion] Can I use Octopoda with GitLab or Bitbucket?
>
> 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](https://docs.octopoda.dev/integrations/ci.md).

> [accordion] What is a credit, and do credits expire?
>
> 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](https://docs.octopoda.dev/billing/plans-and-credits.md).

> [accordion] Can I cancel at any time?
>
> Yes. Your plan stays active until the end of the month you paid for, and you are not charged again. See [Manage billing](https://docs.octopoda.dev/billing/manage-billing.md).

> [accordion] Do you offer refunds?
>
> 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.

> [accordion] Can my team share an account?
>
> Yes, on the Team plan, with up to 5 people. See [Teams and roles](https://docs.octopoda.dev/account/teams.md).

> [accordion] How do I get help?
>
> Email [support@octopoda.dev](mailto:support@octopoda.dev). Include the scan link or the exact error message if you have one.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.