How a tender runs
Four steps, start to finish.
- 1
Create the tender
Set the scope, the deadline, and who is responsible.
- 2
Invite suppliers
Each supplier gets a unique, private invitation link.
- 3
Collect sealed bids
Bids stay sealed — no one can read them before the deadline.
- 4
Open and evaluate
Open every bid together in one logged action, then decide.
The sealed envelope, kept by the server
Not a UI trick — sealing is enforced where it counts.
- Sealed on the server
- Bid prices and contents are withheld by the backend until opening — not merely hidden in the interface.
- Opening is explicit and logged
- Bids open only on a deliberate action, and every access is recorded with who and when.
- Deadlines are real
- The deadline is enforced server-side against real time, so a late bid cannot slip in.
Näidis Ehitus OÜ
Bid submitted 12 Mar 09:41
Deadline passed 14 Mar 12:00
This bid is a demo — open it yourself. In a real tender, the amount is withheld by the server until this exact action.
Built for both sides of the table
For buyers
Run tenders for your organisation with roles, permissions, and a full audit trail. Buyer accounts are set up with you — no public sign-up.
For suppliers
A public tender's public link works with any account; an invite-only tender is visible only to its invited suppliers. Either way, ask questions and submit a sealed bid before the deadline.
View the tenders shared with you.
Public-tender links work with any account; invitation links are personal. Bids stay sealed until the explicit opening.