# Changelog > What is new on the platform and what got better, day by day and newest first. Small fixes and changes you would not notice are left out. To hear of changes without visiting this page, follow [changelog.xml](https://arrangic.com/changelog.xml) in a feed reader. ## 5 October 2026 ### Apps in a workspace **New.** An app in a folder of an npm, pnpm or Yarn workspace now builds. Set its folder as the **Root directory**: the packages are installed from the top of the workspace, and the build and start commands run in the folder of the app. See [Build settings](https://arrangic.com/docs/build-settings.md#an-app-in-a-workspace). ### Domains behind your own proxy **New.** A custom domain can go through a proxy or CDN of your own. The **Domains** page lists one more record for it, marked optional: add it, keep it DNS only, and have the proxy reach the app over HTTPS. Before, the proxy had to be switched off. See [Domains](https://arrangic.com/docs/domains.md#behind-a-proxy-or-cdn-of-your-own). ### Usage budget **New.** The owner of a team can set a usage budget for the billing cycle, under **Team settings**, **Billing**. The owner and the admins get an email and a notification when the usage of the cycle reaches 50%, 80% and 100% of it. The plan fee is not counted. The budget tells you and does nothing else: reaching it never pauses an app. See [Billing](https://arrangic.com/docs/billing.md#usage-budget). ### Apps run without root rights **Improved.** The running app and the deploy commands no longer have root rights. They can write in the folder of the app, in the home folder and in `/tmp`, and ports below 1024 are not open to an app. The install and the build are unchanged. Every app is built again at its next deployment, also when that is a redeploy or a rollback to an older version. See [Build settings](https://arrangic.com/docs/build-settings.md#what-the-running-app-may-do). ## 4 October 2026 ### A step-by-step guide for every new app **New.** A new app shows its next step in the header: every step at a glance, one unfolded at a time. You can hide the guide, and show it again from the settings of the app. ### A notice when an app keeps crashing **New.** When an app keeps crashing, the team gets a notification, and the overview shows what each replica is doing. ### Deploy commands **New.** Commands that run once for every deployment, before the new version takes traffic. The place for database migrations. If one fails, the running app is not changed. See [Deploy commands](https://arrangic.com/docs/deploy-commands.md). ### Your own install command, and more than one build command **New.** Set an install command when the automatic one does not fit, and put several build commands on lines of their own. See [Build settings](https://arrangic.com/docs/build-settings.md). ### Move an app to another region **New.** The **Scaling** page has a region setting. Pick another region, save and deploy again: replicas start in the new region and are checked before the old ones are removed, so the app stays online. A move that fails leaves the app where it was. See [Scaling](https://arrangic.com/docs/scaling.md#move-an-app-to-another-region). ### Limits for variables **New.** An app takes up to 200 variables, 32 KB for one value and 256 KB for all of them together. Names that start with `PLATFORM_` are kept for the platform. See [Environment variables](https://arrangic.com/docs/environment-variables.md#limits). ### Variables during the build **New.** Every variable has a **Build** switch, off until you turn it on. With it on, the variable is set while the app is installed and built: for a token that a private package needs, or a value the build puts into the built files. See [Environment variables](https://arrangic.com/docs/environment-variables.md#during-the-build). ### Wake up fast **New.** A sleeping app can keep its memory, so it answers the next request without starting again. See [Sleep and wake](https://arrangic.com/docs/sleep-and-wake.md). ### Yarn 2 and newer **New.** Projects that use Yarn 2 or newer now build. ### Build logs are kept for 90 days **Improved.** The log of a deployment is kept for 90 days after the deployment ended. ### Build settings are read from your repository **Improved.** When you create an app, the Node version, the package manager and the build and start commands are read from your code. **Detect from repository** on the settings page reads them again. ### New apps stay awake **Improved.** A new app starts with **Keep one replica always on** switched on. Switch it off to let the app sleep when it is idle. ## 1 October 2026 ### Plans, a trial and usage by the second **New.** Three plans, a trial with usage credit and no card, and usage counted per second. The billing page shows what each app used in the current cycle and every line of each statement. See [Pricing](https://arrangic.com/pricing). ### Variable values are revealed one at a time **New.** Owners and admins reveal the value of a variable one at a time, and each reveal is noted in the activity. ### A sleeping app costs nothing to run **Improved.** While an app sleeps, no compute is counted. ## 30 September 2026 ### The first version **New.** Connect a GitHub repository, and every push to your branch builds the app and puts it online. Custom domains with automatic HTTPS, a primary domain that the others redirect to, and a platform URL that can be switched off. Instance sizes and regions, live runtime logs, and environment variables that can be edited one by one or as `.env` text. --- This page on the site: https://arrangic.com/docs/changelog All pages of the documentation: https://arrangic.com/llms.txt