erfa3ly documentation
Deploy Next.js, Laravel, React, Node services, PHP, Docker-first workloads, and static sites—with Git automation, managed databases, domains, and operational visibility.
Start here
Quickstart
Ship your first project from GitHub in minutes
Concepts
Organizations, projects, environments, deployments
Runtime overview
Compare every supported deployment type
Deployment types
Next.js
SSR, App Router, API routes, static export
React & static SPAs
Vite and static frontend bundles
Static HTML
Sites without a Node build step
Node.js services
Express, Nest, Fastify, custom servers
Laravel
PHP, Composer, queues, scheduler options
PHP applications
General PHP + Composer workloads
Custom Dockerfile
Bring your own container image
Platform
GitHub & Git
Installs, webhooks, repository access
Environments & variables
Variables, secrets, preview vs production
Custom domains
DNS verification and HTTPS
Managed databases
MySQL, PostgreSQL, MongoDB
Deployments, logs & analytics
Logs, timelines, retries, analytics
Billing & usage
Plans, invoices, usage limits
Support
Tickets, email, escalation tips
Product pillars
- Detection-first onboarding — Inspect manifests and directories to propose runtime, commands, and Node/PHP versions (always overridable).
- Clear build vs runtime — Static artifacts ship to the edge; containers run behind managed routing with health gates.
- Operational transparency — Streaming build logs, deployment timelines, retries, and project analytics in one place.
- Data adjacent — Attach managed databases where runtimes support wizard provisioning; isolate preview credentials from production.
- Commercial readiness — Organization billing, entitlements, and support workflows for growing teams.
Getting help
Email support@erfa3ly.com, open Support from the dashboard, or check platform status and contactfor broader inquiries.