Prosota
A browser-native planning platform for construction and infrastructure. The schedule is the digital representation of how a project will be delivered — everything else exists to enrich, validate, optimise, or communicate that schedule (NEC/JCT-style construction programmes and beyond).
Built by Prosota Ltd, founded by Louis Oghenemaro (Maro) Sota (Senior Planner / 4D Project Controls Specialist).
What it does
- Scheduling — the heart of the platform: a real critical-path-method engine (hour-precision forward/backward pass, multi-calendar support, dependency logic, DCMA 14-point schedule quality checks, named/saved baselines, resource-loaded activities) — not a wrapper around someone else's scheduling tool.
- Resources — labour/plant/materials assignments integrated directly into the schedule, driving cost automatically.
- Cost Plan — derived from the schedule: fixed and percentage-based cost elements, real computed Earned Value Management (CV, CPI, SPI, EAC, ETC), configurable variance thresholds, rate cards, commitments.
- Analysis — schedule-focused risk and quality: a Risk Register (threat/opportunity split, inherent/residual heat-matrices, mitigation tracking, EMV) alongside DCMA schedule-quality checks and baseline comparison.
- ICD Tracker — Issues, Changes, and Decisions in one integrated change-control tracker, with real approval workflows and audit trails.
- 4D / BIM — federated IFC models (plus GLB/OBJ/FBX) linked to schedule activities and played back on a timeline: Generate Schedule builds a sequenced programme straight from multiple discipline IFCs (levels merged by elevation and geometry, never by storey name); reusable animation profiles (fall, pop, grow, colour/opacity, domino offsets); section boxes, cinematic cameras, perspective/orthographic views; a Realistic Materials render mode with sun/sky lighting, shadows, AO and per-material mapping/colour; image capture and video export at chosen timeline points.
- Every capability cross-links back to the Activities that drive it — a risk can point at the cost line and the schedule activity it actually threatens, not live in its own silo.
Resource Tracking and Profile support selectable Budgeted, Actuals and Earned
Value figures, optional overallocation highlighting, aligned timelines, and
adjustable print spacing. See resource display and print notes
for controls, calculation limits and validation.
Tech stack
| Layer | Technology |
|---|
| Frontend | React 18, TypeScript, TailwindCSS, React Query, Vite |
| Backend | FastAPI (Python), SQLAlchemy, Alembic |
| Database | PostgreSQL |
| Auth | Auth0 (SSO/MFA) |
Status
Active development. The scheduling, cost, risk, and change-control modules are built and in real use; further modules (a controls dashboard, contractor-facing tooling, AI-assisted analysis) are in progress.
Local development
Backend
cd backend
python -m venv .venv
.venv\Scripts\activate
pip install -r requirements.txt -r requirements-dev.txt
alembic upgrade head
python run.py
Frontend
cd frontend
npm install
npm run dev
Requires a local PostgreSQL 16 instance and an Auth0 tenant configured via environment variables.
Vercel database migrations
The backend service build runs deploy_migrations.py using its configured
DATABASE_URL. Production builds (VERCEL_ENV=production) apply Alembic upgrades
under a PostgreSQL transaction lock before deployment. Connection, migration or
schema-version failures fail the build. The Dockerfile is not used by the Vercel
Python service, so its startup migration command does not cover Vercel deployments.
Preview builds only check the schema version and never upgrade a potentially
shared production database. Use a separate preview database and apply
alembic upgrade head to it before deploying a preview containing schema changes.
Production credentials must be available to the backend build as well as runtime.
Testing
Product improvements and implementation status: improvement backlog.
From backend with its development environment activated:
pytest
From frontend:
npm test
npm run build
CI runs the backend test suite against a real Postgres service container, plus the frontend Node tests and production build, on every push/PR to main. Two frontend IFC fixture tests require optional local model paths and are skipped when those files are not supplied.
License
Proprietary — © Prosota Ltd. All rights reserved.
Clash detection and external review: workflow, sharing and SMTP setup.
