FASTAPI ERP Backend Development
Budget / Salary$30–250
TypeFreelance project
LocationRemote
Posted3 hours ago
I’m building a new ERP and need its entire server-side logic crafted with FASTAPI. The stack is already set: asynchronous FASTAPI, MySQL as the primary datastore, and OpenAPI for live documentation.
Core scope
The backend must cover HR, Inventory, Accounts, Sales, Chat Systems and Production workflows straight away, with space to plug in AI agents and a real-time chat subsystem shortly after. Clean separation of concerns is essential so that each module can evolve independently while sharing authentication, authorization, and common utilities.
Security
Full authentication and authorization are mandatory. A JWT or OAuth2 workflow with role-based access control will protect every endpoint, and permission checks will be enforced consistently across all modules.
Architecture expectations
• Async FASTAPI routes using Pydantic schemas
• SQLAlchemy (or another well-supported async ORM) talking to MySQL
• Clear service / repository structure for easy unit testing
• Automatic OpenAPI docs generated from code comments
• WebSocket endpoints ready for the chat module (even if stubs for now)
• Container-friendly setup (Dockerfile + docker-compose) so the whole thing spins up in one command
Deliverables
1. Source code for the above modules, neatly organised by domain
2. Reusable auth package (login, refresh, password reset, RBAC)
3. Database migration scripts and seed data
4. Postman / Swagger collection that demonstrates every route
5. Brief README covering local setup, dev workflow, and deployment notes
The sooner we can get an MVP up, the sooner we’ll iterate on the AI and chat layers, so clean, well-commented code and thoughtful structure matter more to me than piling in features hurriedly.
Core scope
The backend must cover HR, Inventory, Accounts, Sales, Chat Systems and Production workflows straight away, with space to plug in AI agents and a real-time chat subsystem shortly after. Clean separation of concerns is essential so that each module can evolve independently while sharing authentication, authorization, and common utilities.
Security
Full authentication and authorization are mandatory. A JWT or OAuth2 workflow with role-based access control will protect every endpoint, and permission checks will be enforced consistently across all modules.
Architecture expectations
• Async FASTAPI routes using Pydantic schemas
• SQLAlchemy (or another well-supported async ORM) talking to MySQL
• Clear service / repository structure for easy unit testing
• Automatic OpenAPI docs generated from code comments
• WebSocket endpoints ready for the chat module (even if stubs for now)
• Container-friendly setup (Dockerfile + docker-compose) so the whole thing spins up in one command
Deliverables
1. Source code for the above modules, neatly organised by domain
2. Reusable auth package (login, refresh, password reset, RBAC)
3. Database migration scripts and seed data
4. Postman / Swagger collection that demonstrates every route
5. Brief README covering local setup, dev workflow, and deployment notes
The sooner we can get an MVP up, the sooner we’ll iterate on the AI and chat layers, so clean, well-commented code and thoughtful structure matter more to me than piling in features hurriedly.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.