Fewer tools left running
One place for the close, the pipeline, the filings and the approvals, instead of a dozen subscriptions each syncing away in a tab all day.
SUSTAINABILITY
Good work,
Good work,
a light footprint.
Zuger is built to do more with less: less compute, fewer tools left running, nothing wasted to look busy. Here is how, in plain words.
- SERVERS WE OWN
- 0
- HABITS IN THE CODE
- 4
- TRACKERS BY DEFAULT
- 0
- PRICE
- Flat
We run on shared cloud hosting, sized to what is actually used. Nothing sits idle in a rack with our name on it.
Four ways every Run uses less compute, built into the product rather than bolted on.
This site loads no optional cookie or tracker unless you say yes. Lighter pages, and better manners.
Per company, never per token. We earn nothing when an agent uses more compute, so saving it is in our interest too.
THE BIGGER PICTURE
One back office,
instead of a dozen tools.
The greenest compute is the compute nobody needs. A lot of what Zuger does is simply make other work unnecessary.
Done once, done right
An agent prepares the work, you check it and file it. Far less gets redone, re-exported and re-sent because a figure was copied wrong.
On a schedule, not in a rush
Routines run when you set them to, not because someone is waiting, which lets that work take the unhurried route.
SMALL HABITS THAT ADD UP
Four habits,
written into the code.
We built these to keep Runs fast and the price flat. Happily, the same four things keep the footprint small.
- 01
The right-sized model for every step
A Run is a chain of steps, and each one goes to the lightest model that can do it well. Reading a bank line does not need the model that drafts a board pack.
- 02
Nothing is computed twice
What an agent knows about your company barely changes from day to day, so it is cached with the provider and reused, not processed from scratch on every Run.
- 03
Scheduled work takes the slow lane
A routine is not in a hurry. Its Runs go through the provider’s batch path, which uses capacity when it is free.
- 04
Nothing runs to look busy
A model is only called when there is real work: you briefed an agent, a routine is due, or a scheduled check has something to read.
WHERE OUR ENERGY GOES
Simple to explain,
because there is not much of it.
Model calls
Every judgement an agent makes is a call to a model provider. It is the biggest part of our footprint, so it is where the four habits above do their work.
Hosting
The Console, the API and the worker run on shared cloud hosting. The companies behind it are named, openly, on the subprocessors page.
This website
Plain HTML, one stylesheet and one script. No framework and no video. A page here is a few hundred kilobytes, less than one photo from your phone.
STRAIGHT ANSWERS
What we know,
and what we are waiting for.
We would rather give you a plain answer than a nice-sounding one. Here is where things stand today.
| You might ask | Where we are |
|---|---|
| How much CO₂ does a Run produce? | We do not have a real figure yet, because model providers do not publish energy per request. The moment they do, the number goes on this page, per Run, with the working shown. |
| Are you carbon neutral? | We make no claim either way. We have bought no offsets, because we would rather use less in the first place than pay to feel better about it. |
| Do you have a net-zero target? | Not yet. We want a real baseline first, so that a target means something when we set it. |
| Where do your servers run? | Each provider and where it runs is on the subprocessors page, along with the EU residency option you can choose per company. |
Free plan · No card
Care about this too?
If you need something for your own reporting, or you have an idea that would make Zuger lighter, we would love to hear it.