PandaCodeGen / Backend development for portals, CRMs & internal tools
Backend development for customer logins, private uploads, business records and connected tools. We usually build on Supabase, or work with your existing database and APIs. The quote names the data, access rules, integrations and admin screens your application needs.
01 / See the work
Our Panda Patches operations case explains how the application connects staff tasks, records and permissions. It provides concrete implementation evidence for this service.
Project / Panda Patches CRM
A React application backed by Supabase supports orders, production, payments and reporting. The case covers roles and access controls as well as the screens.
Founder-affiliated production system. Its frontend uses React and Vite; it is not a Next.js client case. Sensitive business details are obscured.
Project / A Step Above Medical portal
A portal for class schedules, students, payments and certificates, delivered as part of a live client project.
Independent client project, now live. These screens were captured before launch; no production results are claimed.
02 / Review your site
Managed database and authentication services provide useful foundations. The application still needs a data model, access rules and behavior when something fails.
Identify the source of truth for customers, orders or projects. Map imports, duplicate records and retention requirements.
Define staff roles and customer boundaries. Test denied access as carefully as allowed access.
Map approvals, notifications and external integrations, including retries and repeated events.
Agree logging, backup and restore responsibilities, vendor costs and who responds after release.
What the proposal resolves
The proposal separates platform configuration from the custom application work your team needs.
Design tables and relationships, write versioned migrations and test representative imports. Decide which records may be edited or deleted and by whom.
Configure the agreed authentication flow and enforce access where data is read or written. For exposed tables, review row-level security policies; hiding a button is not access control.
Build the agreed screens and server-side operations. Place privileged credentials outside browser code, and test failed requests, duplicate webhooks and partial updates.
Provide the agreed repository, database migrations, environment setup and runbook. Test the selected backup and recovery process before relying on it.
Website SEO / Search and AI access
A database or login system alone does not make a website easier to find in search. Public pages need their own content and website checks; customer accounts and uploads need their own access rules.
Need ongoing buyer research, page improvements and visibility reporting? AI search services are optional monthly work, scoped separately from the build. Search systems choose which pages they index or cite.
03 / Make the right call
We recommend the scope that addresses the evidence from your site and team, then put the work and boundaries in writing.
Review an existing Supabase app, identify data and workflow risks, and scope specific improvements. An assessment is not a blanket security certification.
Start with the smallest usable portal or staff tool. Add a CMS only if a separate editorial workflow also needs one.
04 / From call to handover
Each stage creates something you can review. Your proposal names the deliverables and the point where you accept them.
Document roles, workflows, existing data and external systems.
Write examples for allowed and denied access, failed integrations and recovery.
Connect one complete workflow from screen to stored record before expanding the application.
Check permissions and failure paths, verify the release process, and document ongoing responsibilities.
05 / Your project price
Quoted to scope
The price is agreed before work starts.
Database design, authentication, custom screens, migration and integrations determine the price. A complete portal is not included automatically in a Starter website build. Discovery establishes the requirements, dependencies and release scope before a fixed proposal.
Named users, records, screens and integrations.
Access, failure and recovery cases agreed before build.
Repository, migrations, account access and operational instructions.
After launch
The build is a one-off. These are the bills that continue, so add them up before you compare quotes.
Supabase
Selected project plan, compute, storage and usage.Frontend hosting
Deployment, server execution and bandwidth where needed.Connected services
Email, payments, monitoring or other providers.Maintenance
Application updates, database changes and support.We build on Supabase's free plan and move the project to Pro, from $25 a month, when it goes live, so you don't pay for the database during the build. The proposal records the plans; usage and reliability requirements decide them.
06 / Ownership & exports
A backend build should identify who controls the business records, accounts and application files. PandaCodeGen includes account control and documentation in its handover. Moving a database is only one part of changing providers: uploaded files, logins, connected services and the application need a separate migration plan.
Your project handover
You receive the project code and design files we create for you, plus documentation and control of the production accounts. If you then take a monthly support or care plan, that doesn't change: we keep sharing the code, documentation and accounts with you, so you always have your own copy. Third-party themes, plugins, services and assets remain under their own licence terms.
For a Supabase project, database records can be exported, but a database backup does not include uploaded files stored through Supabase Storage. Those files need a separate copy, and the application and connected services need their own checks. PandaCodeGen identifies the accounts and responsibilities in the scope and hands over the project code and documentation.
PandaCodeGen hands over the code created for your backend, documentation and control of the production accounts. Another developer can use those materials to assess the application and plan future work. Hosting can move to an account in your name on request or when the engagement ends. Provider plans, permissions and third-party licences still apply.
The project code and design files we create for you.
Instructions handed over with the project files. If you take a care plan later, we keep sharing the documentation with you.
An editing walkthrough at handover, so your team can update the site. Every build that uses Sanity includes training on Sanity Studio and written documentation for it. On Starter, the content editor is set up, documented, and we train you on it.
Control of the production accounts. Hosting moves to your own account on request or when an engagement ends.
Your build keeps working without a PandaCodeGen care plan. Hosting and other provider services still need their own arrangements.
Your written proposal states the details for your project, including any third-party licences.
07 / Before you decide
These are starting answers. Project-specific details belong in the written proposal.
Keep exploring
All services ↗Related service
Custom software and internal tools ↗