SaaS MVP Development based on Cloudflare with Security Features
Budget: €1,500 – €3,000 EUR
This project is an MVP for a SaaS application hosted on Cloudflare with Google-SSO for authentication, a secure database, user authorization, document storage, an audit trail, error logging, and a security concept. Communication must be possible via chat and voice calls (after alignment). There are six defined milestones with an expected runtime of three months.
(1) Collaboration Fundamentals
Each milestone is defined with a fixed price. Payments are split: 60% upon milestone delivery and 40% upon milestone release. Invoicing is done separately for each milestone.
Chat communication (with the requester as the primary point of contact and a response time within one business day, including either a resolution or an estimated date for resolution) (Slack, Teams, etc.) and voice calls (Zoom, Teams). Transparent progress updates and prompt addressing of blockers.
Development and delivery via GitHub (clean commits and clear documentation at the developer's best knowledge). Each milestone is completed with a GitHub release.
Minimal principle: no unnecessary code in debugging tools. Clear separation: GUI, business logic, data handling. Authorization and audit trail are mandatory parts.
MVP implementation within three months. The developer is expected to use a test framework (Jest recommended for flexibility and Next.js compatibility) and include their own test cases for the project.
No iterations or revisions are expected after delivery, as long as the code is functional and meets the agreed-upon milestone criteria.
(2) Core Elements of the Project
Web application (no mobile client), SaaS-capable (multi-tenant).
Each user belongs to a tenant (client). The tenant separation approach will follow the developer's recommendation, while the database scheme will be delivered by the requester. Separate data areas for each tenant.
Login exclusively via Google SSO. Hosting via Cloudflare, with TEST, QUAL, and PROD branches maintained in GitHub. The requester will maintain the Cloudflare environment and use the QUAL branch for automatic deployment. The developer can test independently. Application framework: Next.js for scalability and maintainability. Delivery: code and admin documentation.
User roles: Operator/Developer (sets up tenants and users), Tenant-Admin (full control: create, update, delete), Editor (create and update only), Viewer (read-only access).
English as the default language. GUI texts stored in a dictionary for later translation. Design will be created at the developer's best knowledge, focusing on functionality and minimal styling (CSS-based).
Objects: apartment/house, rooms, areas. Upload and link documents (PDFs, images) to objects. Main report (fields and attachments) generated as PDF. The requester will provide a report template along with the database scheme.
Audit trail: login-logout, changes, creation and deletion of assets stored in the database.
(1) Collaboration Fundamentals
Each milestone is defined with a fixed price. Payments are split: 60% upon milestone delivery and 40% upon milestone release. Invoicing is done separately for each milestone.
Chat communication (with the requester as the primary point of contact and a response time within one business day, including either a resolution or an estimated date for resolution) (Slack, Teams, etc.) and voice calls (Zoom, Teams). Transparent progress updates and prompt addressing of blockers.
Development and delivery via GitHub (clean commits and clear documentation at the developer's best knowledge). Each milestone is completed with a GitHub release.
Minimal principle: no unnecessary code in debugging tools. Clear separation: GUI, business logic, data handling. Authorization and audit trail are mandatory parts.
MVP implementation within three months. The developer is expected to use a test framework (Jest recommended for flexibility and Next.js compatibility) and include their own test cases for the project.
No iterations or revisions are expected after delivery, as long as the code is functional and meets the agreed-upon milestone criteria.
(2) Core Elements of the Project
Web application (no mobile client), SaaS-capable (multi-tenant).
Each user belongs to a tenant (client). The tenant separation approach will follow the developer's recommendation, while the database scheme will be delivered by the requester. Separate data areas for each tenant.
Login exclusively via Google SSO. Hosting via Cloudflare, with TEST, QUAL, and PROD branches maintained in GitHub. The requester will maintain the Cloudflare environment and use the QUAL branch for automatic deployment. The developer can test independently. Application framework: Next.js for scalability and maintainability. Delivery: code and admin documentation.
User roles: Operator/Developer (sets up tenants and users), Tenant-Admin (full control: create, update, delete), Editor (create and update only), Viewer (read-only access).
English as the default language. GUI texts stored in a dictionary for later translation. Design will be created at the developer's best knowledge, focusing on functionality and minimal styling (CSS-based).
Objects: apartment/house, rooms, areas. Upload and link documents (PDFs, images) to objects. Main report (fields and attachments) generated as PDF. The requester will provide a report template along with the database scheme.
Audit trail: login-logout, changes, creation and deletion of assets stored in the database.