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

# Prerequisites

> Install the toolchain and prepare identity, data, encryption, and provider access for a neobank deployment.

# Prepare a neobank deployment

Choose fake local development, loopback live development, one server, or Kubernetes. Live production needs an agreement and account access from Perflo, but Perflo capability-request acceptance is not a startup gate.

## Install the toolchain

| Tool                      | Version         | Required for                     |
| ------------------------- | --------------- | -------------------------------- |
| Docker Engine and Compose | 2.24.4 or newer | Local and server stacks          |
| Python                    | 3.12            | API development and migrations   |
| uv                        | 0.11.32         | Python dependency management     |
| Node.js                   | 24 or newer     | Web development                  |
| pnpm                      | 11.5.2          | JavaScript dependency management |
| Helm                      | 3.x             | Kubernetes deployment            |

## Prepare external services

Production requires:

* Two Auth0 regular web applications for customer and operator sessions
* An Auth0 API audience for agents
* PostgreSQL 17 with a database the migration runner can reach; an empty database is initialized and an existing one is upgraded in place
* Separate Redis 7 authorities for API sessions and Celery task transport
* HTTPS Vault with the derived `neobank-perflo-credentials` Transit key
* HTTPS application origins and authenticated metrics
* Access to the five exact reviewed HTTPS Perflo origins

The server Compose path can run PostgreSQL, two isolated Redis instances, and TLS-enabled Vault on one host. Kubernetes deployments should use managed or separately operated services with equivalent authorization, network, and backup controls.

## Start with fake mode

Run the fake quickstart before live configuration. Fake mode checks customer, operator, operation, approval, mandate, and card flows without external provider state. Then use a dedicated Perflo quality-assurance subject for the controlled live canary.

## Choose the next guide

* [Local development](deploy/local-development)
* [Single-server deployment](deploy/dedicated-server)
* [Kubernetes deployment](deploy/kubernetes)
* [Production readiness](get-started/production-readiness)