Secure Backend Development with Capacity Rules

We are a growing moving company using Base44 as our operational frontend for scheduling jobs, crews, and trucks. We currently rely on Base44’s vendor-managed backend, but we need stronger guarantees around data security, reliability, capacity logic, and long-term platform risk.

We are seeking a skilled developer to design and implement a secure backend architecture where our operational data becomes durable, recoverable, and portable, while Base44 continues to function as the user-facing interface.

Core Objective

Build a backend system that acts as the source of truth for all operational data (jobs, workers, trucks, schedules), enforces real-world capacity rules, and protects the business against data loss, corruption, or Base44 downtime or shutdown.

Current System Context

Frontend: Base44 (used daily by office staff and dispatch)

Domain: Moving operations (crews, trucks, jobs, time blocks, partial-day scheduling)

Users are non-technical; system must be resilient to user error

Real-world constraints

Key Functional Requirements
Resource & Capacity Enforcement

The system must enforce the following business rules at the backend level:

Prevent double-booking of workers across overlapping time blocks

Count unique workers, not assignments, when calculating daily or time-based capacity

Allow the same crew to work multiple jobs in one day only if time blocks do not overlap

Enforce truck capacity limits per time block

Ensure scheduling logic cannot be bypassed through the UI

Data Integrity & Security

Backend-controlled business logic (not only frontend formulas)

Clear separation between user interface and data authority

Role-aware access control to prevent accidental or unauthorized edits

Reliability & Risk Mitigation Requirements

Automated, scheduled backups with retention policy

Documented restore process (tested, not theoretical)

Clear disaster recovery plan covering:

Base44 downtime

Data corruption

Permanent Base44 shutdown

Architecture must allow migration to a new frontend if required

Deliverables

Backend architecture design (diagrams + explanation)

Implemented capacity and scheduling rules

Backup and recovery system

Written documentation covering:

System logic

Failure scenarios and recovery steps

Safe operational use by office staff

Ideal Skills & Experience

Strong backend development experience

Experience designing systems where reliability and data integrity matter

Familiarity with scheduling, resource allocation, or ops-heavy systems

Ability to explain technical decisions clearly to non-technical stakeholders

Comfortable working with an existing SaaS frontend (Base44) Show More