BidPeak documentation
Sell the top spot, and let people fight over it in public.
Before you start
- A server of your own with PHP 8.3 or newer and MySQL 8 or MariaDB 10.6 or newer
- Composer and shell access — it is a Laravel application
- Your own Stripe account. Payments are billed to you by Stripe at their rates; we take no cut
- A domain and an SSL certificate, because it takes card payments
A Laravel application on a server of your own. It takes payments through your own Stripe account, billed to you by Stripe at their rates — we never touch the money and take no cut.
What it does not do
- It does not hold or route money. Payments go to your own Stripe account, billed to you by Stripe — we take no cut and never see it.
- It does not bring bidders. A board is only entertaining once people are on it.
- It is not an auction house: bids are cumulative and never refunded as a matter of course, which is the model rather than an oversight.
- It is the web application. The mobile app is a separate product.
What is in the download
The full Laravel source: boards, listings, the cumulative bidding engine, Stripe payments, the live board and the operator console.
No obfuscation. It is your application, on your domain, taking money into your own Stripe account.
Installing it
Provision PHP 8.3 or newer with MySQL 8 or MariaDB 10.6 or newer and Composer. Get a domain and a certificate in place first — this application takes card payments.
composer install, environment file, migrations, then create the first operator account.
Connect Stripe in test mode and put a bid through end to end before going live. A payment flow that has only been read is not a payment flow that has been tested.
Running a board
Set the opening prices low enough that the first bids happen. An empty board with a high floor stays empty; a cheap board that moves is the advertisement.
Write the rules on the board itself. People will pay to be outbid only if they understand that being outbid is the game rather than a bug.
Use the operator console for refunds and moderation rather than the database. Refunds through Stripe’s dashboard alone leave the board disagreeing with the money.
Licence, updates and support
- One licence covers 1 board, on a server of your own.
- 1 year of updates, from the date of purchase.
- 1 year of email support.
- Instant download + licence key by email
- 30-day money-back guarantee
Questions this page does not answer go to support@webkoding.com. If you bought from us and cannot find your licence key, look it up here.
Common questions
What does ‘cumulative bids’ mean in practice?
Bids are never spent. Taking a position costs more than the bid already holding it, so the price of a rank only moves one way — and it moves because your visitors moved it, which is what makes the board worth watching.
Do you take a cut of the payments?
No. Payments run through your own Stripe account, billed to you by Stripe at their rates. We never touch the money and never see it.
Can I run more than one board?
Yes, each with its own listings, rules and pricing. A directory with several categories is several boards.
Does the board update without a page reload?
Yes. A leaderboard that requires a refresh to show that you have been outbid is not doing the one job a leaderboard has.
What is the difference between this and BidPeak for iOS?
This is the self-hosted Laravel web application — the board, the payments and the operator console. BidPeak for iOS is a separate Flutter project for the mobile app. Buying one does not include the other.