A simple FastAPI template with Flask-inspired blueprint directory structure for small to medium backend projects.
FastAPI Nano is a lightweight, production-ready template for building HTTP APIs with FastAPI. It provides a structured directory layout inspired by Flask's blueprints, allowing developers to organize API logic into separate packages while keeping routing centralized. The template includes authentication, Docker support, and modern tooling to accelerate backend development.
Backend developers and small teams building RESTful APIs or microservices with FastAPI who want a scalable, organized starting point without excessive boilerplate.
It offers a convention-over-configuration approach with Flask-like modularity, built-in production features (authentication, reverse-proxy, containerization), and streamlined tooling—saving setup time while ensuring best practices.
🐍 Simple FastAPI template that mimics Flask's blueprint directory structure
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses Flask-inspired divisional directories to separate API logic into packages like api_a and api_b, making it easy to scale and maintain code for multiple endpoints.
Includes Gunicorn with Uvicorn workers, Caddy for reverse-proxying, and optimized Dockerfiles, reducing deployment friction and ensuring production readiness from the start.
Comes with OAuth2-based JWT authentication and CORS enabled, providing a secure foundation that adheres to modern API security standards without extra setup.
Leverages uv for fast dependency management, Ruff for linting, and pytest for testing, streamlining the development workflow and enforcing code quality.
Ships with hardcoded username and password ('ubuntu' and 'debian'), which is a security vulnerability if not immediately changed in production, requiring manual intervention.
Lacks integrated database ORM or migration tools, forcing developers to manually set up and configure persistence layers for data-driven applications.
Designed for small to medium backend services, so it may not include features necessary for large-scale distributed systems, such as built-in caching or advanced load balancing.