Platform features
What your app can use once it's deployed: build artifacts, edge firewall rules, traffic analytics, logs, and notifications. Replace my-project with your project slug in every example below.
Storage
Every file your build emits is uploaded to object storage and served from there. The Storage page lists the artifacts of your current production deployment — path, size, and last-modified — so you can confirm what actually shipped and download any single file.
Firewall
Block, challenge, or log traffic at the edge before it reaches your site. Rules are enforced by the Deploxa proxy on every request — no code changes needed. Each rule has a type, a value, and an action, can be toggled individually, and tracks a hit count.
| Type | Matches | Example value |
|---|---|---|
IP | A single client IP | 203.0.113.5 |
CIDR | An IP range | 203.0.113.0/24 |
COUNTRY | Requests from a country (ISO code) | RU |
PATH | A request path and everything under it | /wp-admin |
USER_AGENT | A User-Agent substring | curl |
| Action | Effect |
|---|---|
BLOCK | Reject with a 403 error page |
CHALLENGE | Reject with a 401 "authentication required" page |
LOG | Allow the request but record it in the firewall log |
Rules are evaluated in order and the first match wins. Start a new rule on LOG to see what it would catch, then switch it to BLOCK once you're confident it isn't catching real visitors.
Fail-open by design
Analytics & speed
Every request served through Deploxa is recorded as an anonymous visit — the client IP is hashed, never stored. Each visit captures path, referrer, country, and device/browser/OS, which powers the traffic, top-pages, and audience breakdowns with zero setup. Speed Insights adds server response times, latency percentiles, and error rates per route.
Logs
Build and runtime logs are captured automatically — no agent, no SDK. Filter by deployment, level, and text on the Logs page, and export the result as JSON or CSV.
Deploy hooks & notifications
Deploy hooks (inbound)
A deploy hook is a secret URL that queues a deployment when you POST to it — for headless CMS publish events, nightly rebuilds, CI pipelines, or a Slack slash command. Create one under Project → Settings → Deploy Hooks, choose the branch, and copy the URL. It can't be viewed again after creation.
curl -X POST https://deploxa.com/api/hooks/dh_a1b2c3d4e5f6
POST only. The request body is ignored — the branch comes from the hook's own configuration.Outbound notifications
Point Deploxa at a Slack or Discord webhook URL, or your own endpoint, and it will POST there when a deployment changes state. Configure under Project → Settings → Webhooks.
| Event | Fires when |
|---|---|
deployment.started | A build begins |
deployment.ready | A deployment goes live successfully |
deployment.failed | A deployment fails |
deployment.rollback | Production is rolled back to an earlier deployment |
Slack and Discord targets get a formatted message; a custom target gets a JSON body with the event name and deployment context. Failed deliveries retry with exponential backoff up to the limit you set, and every attempt is visible in the delivery log — if three consecutive deliveries fail, the org owner is emailed once per day.