Releases

Rebuilt logs and clearer deploys

A pass over the parts of the product you actually watch while shipping. Build logs are complete and stream live, the Logs page was rebuilt around the deployment you care about, and the platform now tells you up front when it cannot build a repository.

Logs

• Build logs are captured in full — the builder batches its output, so a long install step no longer trips the ingest limit and truncates the log
• Rebuilt project Logs page — pick a deployment, then switch between its build and runtime output
• Build logs replay and then continue live, so opening the page mid-build shows everything from the start
• Runtime logs now work for Next.js SSR projects, not just Node.js functions
• Search and level filters moved onto the Logs page itself
• Runtime logs look back 15 minutes when you connect, instead of starting from the moment you opened the page

Deploys

• Repositories the platform cannot build are flagged before you start, with the reason, instead of failing partway through a build
• The build output directory is detected after the build when it is not configured, so projects that emit to build/ or dist/ no longer need manual setup

Domains & security

• The custom-domain setup screen shows the correct A record for the platform edge
• Firewall rules and the admin IP allowlist resolve the true visitor IP from the edge

Site & docs

• Status and release pages are readable without signing in
• Every public page carries a real title, description and canonical URL
• The sitemap is generated from the documentation navigation, so it cannot drift from the pages that actually exist

Architecture tour and a rebuilt docs set

A clearer picture of what the platform does with your code, and a documentation set organized around tasks rather than screens.

Platform

• New public architecture page — an interactive diagram of how a deploy travels from Git push to live URL, with the data-flow scenarios behind it
• Documentation consolidated into eight task-focused guides across Getting Started, Deploying, Running your app, and Workspace

Logs

• Build and runtime log streaming runs in the dashboard itself — same-origin, and authorized by your session rather than a separate token

Analytics

• Edge metering is batched — a page that loads dozens of assets now costs a single write instead of one per asset
• Metrics flush on shutdown, so an update to the edge no longer drops the counts buffered at that moment

Live build status and honest usage numbers

See a build move through its phases as it happens, and trust the numbers on your usage page.

Deploys

• Watch the build phase update live — queued, building, deploying, then ready or failed — without reloading the page
• A new deployment is reachable on its domain as soon as it is ready; a race could previously leave a deployment marked ready while its domain served 404s

Performance

• Server-rendered responses stream from the function instead of being buffered, so time to first byte tracks your app rather than the size of the response
• Slow cold starts get timeout headroom and finish rendering, instead of returning a gateway error

Analytics

• Page requests count only real document loads — client-side prefetches no longer inflate your usage
• Firewall rules and unique-visitor counts see the real client IP, not the edge's own address

Deploys that tell you what happened

The first release after launch, aimed squarely at builds that failed quietly. A deployment now always reaches a final state, and its logs actually contain the build.

Deploys

• A build that dies before it can report now surfaces as a failed deployment instead of sitting queued indefinitely
• Deployments stuck mid-build are reconciled automatically and their build slot released
• Deploying with an expired GitHub connection fails immediately with a message telling you to reconnect, instead of creating a project and a build that cannot clone
• Push-triggered deploys, deploy hooks and deploy tokens honor the same plan exemptions that manual deploys already did
• Free plan monthly deployment limit raised from 10 to 15

Logs

• Ordinary build output is stored — previously only status-change lines survived, which is why build logs looked nearly empty

Dashboard

• Project overview shows a live preview image of the deployed site
• Project and workspace navigation regrouped into sections
• Onboarding and plan-selection fixes

Initial release

The first release of Deploxa — connect a repository and go from a Git push to a live URL, with the domains, logs, and analytics a real app needs.

Deploys

• Connect a GitHub repository and auto-deploy on every push
• Manual deploy wizard — pick a branch, confirm build settings, and edit environment variables
• Upload deploys for prebuilt static sites (drag & drop a folder)
• One-click redeploy of the current branch
• Promote a deployment to production, or instantly roll back
• Per-branch preview deployments
• Static sites, Node.js functions, and Next.js SSR on Lambda via OpenNext

Domains & networking

• Custom domains with automatic SSL
• Edge caching with one-click cache purge
• Firewall rules by IP, CIDR, country, path, and user agent

Storage & data

• Build artifact browser for the live deployment
• Encrypted environment variables, applied at build time
• Per-branch deploy environments with variable targeting

Logs & analytics

• Real-time build and runtime logs with search and JSON/CSV export
• Project metrics — edge requests, function invocations, and error rate
• Privacy-safe visitor analytics and Speed Insights

Collaboration & platform

• Organizations and teams with role-based access
• Deploy hooks, deploy tokens, and webhook integrations
• Usage-based billing and limits
• Public status page with incident tracking