Brewless Brewless Docs

Running your application

Saving costs

What the Savings page in the console checks, where its amounts come from, and how to hand a tip to a coding agent as a prompt.

On this page

A serverless container is billed for the seconds it runs and the memory it was given. That makes an application cheap when it sleeps — and it makes a wake-up that nothing needed a line on your bill. Savings, under Costs in the console, names the places where you pay for something you may not need, and an application's own page shows the same findings for that application alone.

Everything on the page comes from what Brewless already knows: the hours it recorded of every container and database, the settings your last deploy applied, and how each environment was set up. No provider is asked and no container is woken, so the page costs you nothing to open.

Four figures stand above the list: what the measured findings come to a month, what the ones worth checking could add to that, how many findings there are and over how many environments. Under them every finding carries the mark of its kind, with its amount in the margin.

Measured, or worth checking

A finding is measured when the amount follows from the hours Brewless recorded. It is worth checking when the amount also depends on something Brewless cannot see from out here: whether your application has any scheduled tasks, whether it fits in less memory. What was looked at and came out fine is kept apart under Also looked at, so you can see it was looked at.

Amounts are estimates from Scaleway's list prices, before tax, and the page names the date those prices were read. They are not lines from your invoice; Costs shows what the providers actually charged.

What it checks

Finding What it is
A worker that is up nearly always It is being asked for jobs by the minute rather than called when there are any. What it ran is what it costs.
A web container that hardly sleeps Something keeps waking it: a public page that cannot be kept at the edge, a monitor, a crawler.
The edge cache switched off With edge.cache: 0 every visit reaches the container itself.
A container kept warm A minimum above zero keeps it running every hour of the month.
A roomy container It has 2 GB or more and never needed a second replica, and memory is what you are billed for.
A database awake most of the time Over the same hours, the smallest managed node would have cost less.
A database minimum above one vCPU While it is awake it is billed for that minimum whether it uses it or not.
A standby copy outside production A standby in another zone is a second instance, billed as one.
An environment nothing was released to Its containers may sleep, but a database, a bucket and a pull zone do not.

The checks need recorded hours: Brewless counts them per hour, so it takes about a day before the page can say anything, and it then reads the last 30 days.

A tip as a prompt for your agent

Three of the findings are about the application itself, not about brewless.yml, and those cannot be settled from the outside. Each one has a Copy prompt button: it copies a task for a coding agent with this environment's own figures written into it — what the page you are on wakes, what the container ran, how much memory it has. Copy every tip as one prompt does the same for all of them at once.

The prompts ask for a report, not for changes: they end with "change nothing until I say so", so you read what your agent found before anything is touched.

What they look into:

  • the web container that will not sleep — which public routes give a visitor without a cookie a session, a CSRF token or a Set-Cookie, which middleware starts a session where it need not, and what asks the application on a timer. See Edge cache for what the edge can keep;
  • the worker that is up — every scheduled task with its cron expression, how often it really has to run, and whether the application has any scheduled tasks at all. See Queues and the schedule;
  • the roomy container — what a request and your heaviest job really use at their peak, and what makes them heavy, before you lower the memory in brewless.yml. See Scaling.

Note

Brewless only advises here. Nothing on this page changes an environment: every finding names the key in brewless.yml or the page where you make the change yourself.

Who can see it

Savings sits behind the same permission as Costs. A member whose Costs is closed does not see the page or the panel. See Members.