Getting started
Connect a repository, deploy to the edge, and ship your first production release on Easel.
This guide walks through your first deployment: connect Git, get a preview URL, and promote to production.
1. Create a project
Sign in at app.easel.sh and create a workspace if you do not have one yet. Import a Git repository from GitHub or your connected provider. Easel detects your framework and sets build defaults automatically.
2. First deploy
When you connect a repo, Easel runs an initial build and deploy. Open the deployment detail page to watch build logs, inspect the output, and copy the generated URL.
Preview deployments use commit-specific and branch-specific URLs so you can share a build without touching production. See Deployment URLs for how those URLs are structured.
3. Preview on every push
Pushes to branches other than your production branch create preview deployments. Each pull request gets an isolated URL you can share with reviewers.
For how preview and production environments differ, see Environments.
4. Ship to production
Set your production branch in Project Settings → Environments (for example main). Pushes to that branch update your production URL automatically.
Production deployments can also use custom domains. Attach a domain in project settings and Easel provisions TLS.
5. Protect traffic at the edge
After your first deploy, configure custom Web Application Firewall (WAF) rules to log, challenge, or block unwanted traffic. Review how rules interact with attack challenge mode before enabling site-wide protection.
Next steps
CLI
Authenticate, link projects, inspect deployments, and read logs.
Environments
Preview vs production behavior and branch configuration.
Custom domains
Attach your hostname and get automatic TLS.
Environment variables
Scope secrets to production and preview.
Easel CDN
Caching, headers, compression, and TLS for every deployment.
Custom WAF rules
Match requests at the edge with Log, Deny, Challenge, Bypass, and Redirect.