Terms

Terms of service

Version 2026-08-25-draft. This is a draft pending legal review. The auction mechanism described below is what the software actually does, and the version above is recorded with every bid so any bid can be read against the exact terms it was placed under.

The auction. Access to a Distrosauce workspace is sold through a daily sealed-bid uniform price auction. You bid a monthly price. When the auction clears, the highest bidders up to the number of slots offered that day win, and every winner pays the same clearing price, which is the highest losing bid. You never pay more than you bid.

Your bid. Bids are sealed. Nobody, including other bidders, sees your amount. A bid is a commitment for that day only: it does not roll over, and you may raise it but not lower it while the auction is open. Bid amounts and their timestamps are assigned by our servers and are not editable after the fact.

Payment. When you bid, your card is saved through Stripe. Nothing is authorized and nothing is held. If you win, the clearing price is charged as the first month of a monthly subscription. If you lose, nothing is charged. If the charge fails, the slot is left unfilled and no other bidder is promoted into it.

Subscription and price. Winning starts a month-to-month subscription at the clearing price. You may cancel at any time. There are no refunds for a month already in progress. Your price is held for twelve months from the date you win.

What you are buying. A workspace and the runtime. Distrosauce is bring-your-own-key: you supply your own model API keys and your own sending tools. We do not resell those and we do not mark up their usage.

Card details. Card data is collected by Stripe and never reaches our servers. We store only identifiers issued by Stripe.

Cancelling. Cancel from the Stripe billing portal link in any receipt, or by asking us. Cancellation takes effect at the end of the month you have already paid for. We do not cancel anyone automatically. If a renewal payment fails, Stripe retries on its own schedule and we email you; nothing about your workspace changes automatically while that happens.

One workspace per account. An account that already has a workspace cannot bid. If you win while already holding one, the charge is not made and the slot is left unfilled rather than billing you twice for a single thing.

Disputes and chargebacks. Every auction is reconstructable from our records: what was bid, when, by whom, what the clearing price was, and what you were charged. If you think something is wrong, ask us before raising a chargeback and we will show you the reconstruction.

What we keep. Your bids, their amounts and server timestamps, and the outcome of every auction you entered, for as long as we operate. That record is what makes a dispute answerable, so we do not delete it on request while a payment relationship exists.

If we stop. If we discontinue the service we will stop taking bids, cancel active subscriptions, and not charge another month. We do not promise a refund of a month already in progress.

Open questions for review. This draft is honest about what is not settled. The items below are places where the software does something specific and these terms either say nothing or would be promising something nothing enforces.

The price lock is policy, not code. We say your price is held for twelve months. Nothing in the software enforces that; it is kept by not repricing. There is no repricing feature at all today. A reviewer should decide whether that promise should be in the terms in this form.

Notice before a price change. The marketing design promised thirty days notice before any price change. Nothing sends that notice, and no such notice mechanism exists. It has been left out of these terms rather than promised and not delivered. If it should be promised, something has to be built to send it.

Whether we bid in our own auction. Nothing in the software prevents us from bidding in our own auction, and the operator surface can see bid amounts in an open auction before it clears. Every one of those views is recorded in an audit trail that cannot be skipped, so the record exists. That is a record, not a prohibition. Whether these terms should commit to not doing it is a question for review, not one we resolved ourselves.

Entity, governing law, and notice address. Not stated anywhere on this page yet. They need to be.