erfa3ly
LoginGet started

How erfa3ly works

Mental model for organizations, projects, environments, deployments, and routing—so you know where to look in the dashboard.

Organizations

Everything belongs to an organization: projects, deployments, domains, databases, billing, and team access. Switch organization from the workspace selector to manage a different customer or team space.

Projects

A project connects your Git repository (usually GitHub) to a runtime kind—for example Next.js SSR, a static React build, Laravel, or a custom Dockerfile. Projects hold default build commands, Node or PHP versions, output directories, and links to environments.

Environments

Each project has one or more environments (for example Production and Preview). Environments isolate configuration: branch or deploy rules, environment variables, and which deployment is currently live for that environment’s hostname.

Deployments

A deployment is a single version built from a commit. Creating a deployment clones your repo, runs install/build steps appropriate to the runtime, publishes static assets or starts a container, runs health checks where applicable, and wires traffic through the edge. You can trigger deployments from the dashboard, via API, or automatically from GitHub webhooks.

Build vs runtime: Static runtimes publish files to edge storage—there is no long-lived server process. Container runtimes (SSR, Node services, PHP/Laravel, custom images) run behind the edge proxy with health-checked loopback routing.

Automatic detection

When you connect a repository, erfa3ly can inspect manifests (package.json, composer.json, next.config, lockfiles, and directory layout) to suggest a runtime and commands. You can accept detection or override fields in project settings and the create wizard.

Where to go next