Use the local login convention
The current API uses Nepal phone numbers as login IDs. Email-only login and Google sign-in are retired.
The tradeoff
This narrows supported registration to Nepal phone numbers.
← All projectsRestaurant software
Buwigs Eats
A restaurant platform designed around accountable access.
The challenge
Restaurant operators and platform administrators need different controls over accounts, applications and day-to-day operations.
Project scope
- Restaurant administration
- Nepal phone login
- Controlled onboarding
Decisions behind the build
Separate registration from approval
Registration creates an account immediately, while restaurant applications require superadmin approval.
The tradeoff
The interface must distinguish an account from permission to operate a restaurant.
Apply migrations before serving requests
The container waits for PostgreSQL and applies Alembic migrations before the API starts. A migration failure stops startup.
The tradeoff
Availability during deployment depends on a successful, compatible schema upgrade.
What took shape
A restaurant application and API with a defined approval boundary and a deployment process that checks the database schema before serving traffic.
Built with
FastAPI · PostgreSQL · Next.js
Based on the project implementation and documentation. Tradeoffs explain the implications of these choices; no measured business results or client feedback are claimed.
Let's build something impactful together
Ready to turn your vision into production-grade software? Let's start the conversation.
Start Your Project