Convert App to Multi-Tenant Architecture
Budget: ₹12,500 – ₹37,500 INR
I currently run one codebase per customer, each on its own sub-domain backed by its own database. Maintaining and updating these parallel installations has become slow and expensive, so I need the application refactored into a true multi-tenant setup served from a single URL.
Architecture change
– A shared database is the goal, but each customer must still have completely isolated data. I believe the cleanest way is separate tables for each tenant inside that shared database; I’m open to your advice on naming conventions, sharding strategies, or other proven patterns that keep queries fast and maintenance simple.
User management & security
– The new build has to support role-based access control (RBAC) so that each tenant can create admins, power users, viewers, etc. I haven’t locked down an authentication method yet, so feel free to suggest whether we stay with basic email/password or add social logins or SSO.
Migration path
– You’ll also need a practical plan (and scripts) to migrate existing customer instances into the single database without data loss or downtime.
Deliverables
• Refactored codebase running a single multi-tenant instance
• Database schema and migration scripts implementing per-tenant tables
• RBAC layer integrated in the app UI and API
• Clear documentation covering setup, tenant onboarding, and future scaling steps
If you have solid experience turning single-tenant apps into scalable multi-tenant platforms, I’d love to see how you’d tackle this.
Architecture change
– A shared database is the goal, but each customer must still have completely isolated data. I believe the cleanest way is separate tables for each tenant inside that shared database; I’m open to your advice on naming conventions, sharding strategies, or other proven patterns that keep queries fast and maintenance simple.
User management & security
– The new build has to support role-based access control (RBAC) so that each tenant can create admins, power users, viewers, etc. I haven’t locked down an authentication method yet, so feel free to suggest whether we stay with basic email/password or add social logins or SSO.
Migration path
– You’ll also need a practical plan (and scripts) to migrate existing customer instances into the single database without data loss or downtime.
Deliverables
• Refactored codebase running a single multi-tenant instance
• Database schema and migration scripts implementing per-tenant tables
• RBAC layer integrated in the app UI and API
• Clear documentation covering setup, tenant onboarding, and future scaling steps
If you have solid experience turning single-tenant apps into scalable multi-tenant platforms, I’d love to see how you’d tackle this.