Automatic scaling
Capacity follows demand rather than a fixed plan. As bidders arrive in the closing phase the platform expands, and contracts again afterwards. This was built for customers whose auctions concentrate thousands of bidders into the last minutes of a sale, and it is the reason those sales complete instead of timing out.
Microsoft Azure
The platform runs as cloud services on Azure, in the West Europe region — physically in the Netherlands — using Azure's infrastructure for redundancy, security and scale. The platform is monitored continuously, and maintenance happens without taking your auction down. Storage and traffic are not metered on any plan — catalogue as many lots, with as many images, as your sales need. Plan contents are on the pricing page.
Services, not a monolith
The bid engine, the Manager, the APIs, the authentication service, the event system and the apps are separate services with defined interfaces between them. Practically, that means three things: parts can scale independently under load, a change to one does not require redeploying the others, and you can adopt some without adopting all.
Multi-tenant, with real isolation
More than twenty-five auction houses run on this stack, and each one has its own database — not a shared table with a customer column. Which tenant an API call belongs to is resolved from the access token itself, so an integration can only ever reach its own data. That is the kind of isolation an auditor accepts without a meeting.
Configured, not coded
The platform carries 265 configuration settings — fees, VAT, bidding behaviour, registration, email, branding — and 16,460 translatable interface strings, down to individual button labels. That pair of numbers is what “configurable” means in practice: a wine house and a machinery liquidator behave differently because they are configured differently, not because either paid for custom code. Search runs on a dedicated index, so bidders filter tens of thousands of lots on the fields each auction house defines for its own goods.
Track record under load
In the early 2000s we ran the platforms behind Troostwijk and BVA, then the largest auction portals in Europe. After their acquisition, businesses from the same ecosystem — Epic Auctions among them — continued with us. Handling European portal-scale traffic is not a projection for us; it is a thing that already happened.
What this covers in full
The full feature list →Platform and architecture on the full list →
- Twenty-five-plus auction houses on one stackThis is not built for you from scratch. It already runs live sales for more than twenty-five auction businesses.
- A separate database for each tenantYour data sits in its own database, not in a shared table with a customer column. Isolation your auditor will accept.
- Tenant resolved from the access tokenYour integrations can only ever reach your own data.
- Azure hosting that scales automaticallyThe last five minutes of a sale, when everyone bids at once, is the moment the platform is built for.
- Fast search across lots and auctionsBidders search a catalogue of tens of thousands of lots and get results instantly.
- Faceted search driven by configurable fieldsThe filters on your site come from the fields you defined, so a wine sale filters by vintage and a car sale by mileage.
- 265 configuration settingsFees, VAT, bidding, registration, email, branding — configured for your business rather than coded for it.
- Settings scoped separately for Manager and websiteThe same setting can behave one way for staff and another for bidders.
- Three ways to run the front endTake our hosted site, add auctions to the website you already have, or build your own on the API.
- Blazor and Drupal front endsTwo proven front-end stacks, or your own — the platform does not force one on you.
- White-label apps for iOS and AndroidYour own app in the App Store and Play Store, under your name, not ours.
- CDN image delivery, resized on requestCatalogue photos load fast for bidders anywhere, at the size each screen needs.