First, the week we did not post
We skipped last Saturday. basedhack put real traffic on the proxy, and real traffic finds things. The week that followed was bug fixes and rough edges, not features, and none of it was worth dressing up as a release. So we stayed quiet and kept working. This post is where that work shows up.
A quiet week, by the numbers
basedhack was a spike. Thirty teams pushing at once moved four billion tokens in a weekend. This was the opposite of that: no event, no crowd, just the proxy doing its job for the people who run through it every day. Here is what a normal week looks like.
Smaller than the hackathon, and that is the point. A spike shows the ceiling. A quiet week shows the floor, and the floor is where the savings actually live.
What shipped
Aggregated and plainly stated, here is the shape of the release. Three things, one direction: condense is getting ready for teams that need more than a personal key.
Organizations are live
You can now run condense as a team. An organization has one shared credit pool that the whole group draws from, a per member budget so no single person can spend the entire balance, and one spend cap that bounds the group as a whole. Invite your people, decide who can spend what, and the numbers take care of themselves.
Every member sees their own standing right on the dashboard now: how much they have left, and the cap it sits inside. Billing lives in one place. Control stays with the owner. Nobody has to ask how much room is left, because the answer is on the screen in front of them.
Install once, then forget it
The client got the cleanup it needed. Setting condense up used to ask too much of you, and it asked again more often than it should have. That is fixed. You install once: a single command brings the client down, wires your profile, and keeps itself current after that. Starting a session is one step. The friction that used to sit between you and the proxy is gone, and the dev experience is the better for it.
And because it is your machine the client runs on, the client is open. dense is MIT licensed and lives in the open at github.com/condense-chat/dense. Every release is built from tagged source, and the install script is byte identical to the one we serve, so you can read exactly what runs before you run it.
Groundwork for the enterprise
Bigger teams ask harder questions before they hand a proxy their context, and they are right to. So the rest of this release is groundwork rather than surface, and three pieces of it landed this week. Zero data retention is now a flag you can set per key, per user, or for the whole account: when it is on, request content is never written down, it lives in memory only long enough to return your response. GDPR export and erasure are wired end to end, so a user can pull a full copy of their data or have it deleted for real, right down to severing the link to their identity. And an append only audit trail now stands behind every privileged action, tamper evident, with identifiers hashed and IP addresses truncated before anything is stored.
None of this is the whole story. The full set of controls, what we can and cannot see, where the data lives, how we respond to an incident, is written out on the security page.
SOC 2, coming soon
The independent audit is underway, and we expect our SOC 2 report soon. When it lands, the teams that need it for procurement will have it in hand, and we will say so here the Saturday it does.
Soon: a prize for the most saved
One more thing taking shape. Every quarter we want to reward the team and the builder who compact the most. The numbers already live on the leaderboard; soon there will be something real attached to the top of it. We will share the details once it is ready to announce.
Back to weekly from here. See you Saturday.
Run your team on the cheaper bill.
Sign up, wait for approval, install the client once.