Building better competitions

Competition infrastructure you can prove.

Run the storefront, customers, competitions, draws, compliance and growth from one platform.

And when somebody asks how the winner was chosen? Show them.

Your brand. Your customers. Your data. Built on Beaver.

Boab, the BeaverComps beaver, arms folded, watching the system run.

What the platform gives an operator

  1. PROVE

    Verifiable draws

    Entry lists are committed before winner selection. Results can be independently checked.

  2. PROTECT

    Rules built into the platform

    Spend controls, exclusions and audit records happen inside the operation.

  3. RUN

    One operator console

    Create competitions, manage players, run draws, track fulfilment and see the numbers.

  4. GROW

    Growth built around the customer

    Campaigns, journeys, referrals, loyalty and memberships without bypassing player protections.

  5. OWN

    Your data stays yours

    Export players, orders, entries, draws and audit records from the console.

  6. HOLD UP

    Infrastructure built for the rush

    Storefront content is served at the edge, with critical transactional work kept where it belongs.

Public draw verification, enforced compliance controls, console exports and edge served storefronts are Live today. Referrals, loyalty, VIP, memberships and customer journeys are Built: in the product, not yet proven with live operators.

Prove

Fair should not mean "trust us".

Most competition results ask the customer to trust the operator, the platform and whatever sits behind the draw button. Beaver takes a different approach.

Before a draw runs, the entry list is frozen and a cryptographic fingerprint is published. The source of randomness is identified before that randomness exists. When the result is produced, the values needed to check it are public. No hidden winner picker. No editable outcome. Evidence.

  1. 1Commit the entries
  2. 2Reveal the randomness
  3. 3Select the winner
  4. 4Check it yourself

Entry list 1,000 entries

A window on to 7 of the 1,000 entries. You do not need to read them: the checks below prove whether this list is the one that was committed.

Commitment (SHA-256 of the list)

Not committed yet

Randomness

Named before the draw, published after. Nobody knows it yet.

Winning ticket

Pending

Verification

  • Entry list matches its commitment
  • Randomness was named before it existed
  • Winner recomputes from the published values

Press Run the draw to start.

A demonstration of the method, running in your browser. It is not a live Beaver draw, and it does not use Beaver's exact algorithm or randomness source. The "randomness" here is a stand-in for a public value published after the entries are committed.

Live The Beaver draw engine supports committed entry lists, future public randomness, tamper refusal, unbiased selection and a public verifier.

Protect

A policy page cannot stop a transaction. Beaver can.

Competition businesses have rules to operate under. Those rules are more useful when the software actually enforces them. Beaver Compliance turns requirements into platform controls.

  • Spend limits can stop checkout.
  • Self exclusion can stop access.
  • A care flag can stop marketing.
  • A missing launch requirement can stop an operator going live.

Sensitive changes leave a record of who changed what, when and why. And Beaver can produce a dated evidence pack showing which controls were active during a period.

Compliance should be machinery, not decoration.

Audit record

    Illustration of where enforcement happens, with example values. Not the Beaver product interface.

    Run

    Run the whole operation.

    A competition platform should do more than put prizes on a website.

    Beaver gives the operator one place to build competitions, manage their lifecycle, run and verify draws, track prizes, understand revenue, work with customers and control the rules underneath it all.

    Live Self service signup, guided setup, readiness checking, competition management, draw room, fulfilment, player management, finance, billing, compliance and campaigns.

    Operator Console
    • Setup
    • Competitions
    • Draw room
    • Players
    • Fulfilment
    • Finance
    • Compliance
    • Campaigns
    • Settings

    Launch readiness

    • Brand applied (done)
    • Legal pages published (done)
    • Compliance controls set (done)
    • First competition scheduled (outstanding)

    Not ready to go live. One required step is still open.

    Competition lifecycle

    1. Draft
    2. Scheduled
    3. Live (current stage)
    4. Closed
    5. Drawn
    6. Fulfilled

    Illustration of the console structure. Real screenshots will replace it.

    • Build competitions

      Set the prize, price, ticket pool, purchase caps, schedule, imagery and competition details.

    • Know when you are ready

      Beaver's readiness checks stop a competition site going live while required setup is still missing.

    • Run the draw

      Commit the entries, execute the draw, publish the result and make it verifiable.

    • Manage players

      See account information, entries, spending history and relevant account activity.

    • Track the prize

      Record what is owed, age checks, dispatch, delivery evidence and fulfilment timing.

    • See the money

      Revenue, VAT, margin and platform billing in the same operating environment.

    • Control the platform

      Settings are managed centrally, with sensitive staff actions recorded.

    • Keep the evidence

      Audit records of sensitive changes and dated compliance evidence, from the same console.

    Grow

    Getting the first customer is only the start.

    Beaver is being built for operators who want a business, not a revolving door of one off buyers.

    The growth layer connects customer data, campaigns and retention mechanics inside the same platform that knows who bought, what they entered and whether they should be contacted at all.

    • Campaigns

      Live

      Build and send campaigns against real customer audiences.

    • Customer journeys

      Built

      Automated flows for moments such as welcome, draw reminders, winners and win back.

    • Referrals

      Built

      Reward genuine customer acquisition after the referred customer's first settled order.

    • Loyalty

      Built

      Reward customer activity using points held through the platform ledger.

    • VIP

      Built

      Create spend based membership tiers and benefits.

    • Members clubs

      Built

      Run recurring memberships with operator defined benefits.

    Growth does not get to route around protection.

    Marketing preferences, frequency controls and player protection remain part of the system.

    Own

    Built so you can leave.

    A platform should earn the right to keep your business. It should not trap it.

    Your operator data can be exported from Beaver, including players, orders, entries, draws and audit records.

    Your brand remains yours. Your customer relationship remains yours. Your business remains yours.

    We would rather make leaving easy and give you a reason to stay.

    Live Full console export. There is no public API claim here, on purpose: that is not ready to sell.

    Export operating data
    • PlayersExport
    • OrdersExport
    • EntriesExport
    • DrawsExport
    • Audit logExport

    Your data. Your file. Taken from the console, not requested from a supplier.

    Illustration of the export list. The five data sets shown are the ones the console exports today.

    Built to hold up

    When everybody arrives at once, the homepage should not be the problem.

    Competition traffic is rarely polite. A campaign lands. A prize catches fire. A deadline approaches. Everybody turns up.

    Beaver's storefront architecture serves cacheable pages at the CDN edge while keeping live information dynamic and reserving critical database work for the paths that actually need it.

    Edge served storefront

    Public competition content can be served closer to the visitor.

    Critical paths stay critical

    Checkout remains transactional rather than turning every page view into database work.

    Operators stay isolated

    Each operator runs within its own process environment.

    Keep the public experience light. Keep the important work controlled.

    Live Edge caching and per operator process isolation. We will publish traffic numbers when we have earned them.

    Built different

    Starting should not require a software project.

    You bring the brand. Beaver creates the operating environment.

    From the console, an operator can move through branding, legal pages, competition setup, required controls and launch readiness without somebody manually building a new server for every customer. The platform checks what is missing before it lets the site go live.

    1. Create operator

      A self service signup creates the operator environment.

    2. Add brand

      Colour, accent, logo, font and corner style.

    3. Complete setup

      Legal pages, controls and the first competition.

    4. Pass readiness

      Missing requirements block launch, with the reason shown.

    5. Go live

      Only once the checks pass.

    There is no public signup on this website yet. Setup starts with a demo.

    Because finding out after launch is a rubbish onboarding strategy.

    Another competition platform?

    Not interested.

    There are already plenty of ways to launch a competition website. That isn't the problem Beaver was built to solve.

    We are building the infrastructure behind serious competition businesses. Infrastructure that can explain what happened. Infrastructure that can enforce how the operation should behave. Infrastructure the operator remains in control of. And infrastructure that keeps getting better without pretending tomorrow's roadmap is today's product.

    • If it is live, we'll show you.
    • If it is built, we'll tell you.
    • If it isn't ready, we won't sell it as if it is.

    The Lodge

    Learn how the whole thing works.

    The Lodge is for people building and running competition businesses. No weekly content quota. No 900 word answer to a 30 second question. Just useful explanations of the technology, operation and rules behind the category.

    Meet Boab

    He likes things built properly.

    Boab is Beaver's resident builder, inspector, explainer and occasional sceptic.

    You'll see him poking around the platform, checking the evidence and asking the question worth asking: does it actually work?

    Usually, he already knows the answer.

    Questions

    Asked and answered

    What is BeaverComps?

    BeaverComps is software for running an online competition business. It brings together the customer storefront, competition management, draws, player accounts, compliance controls, campaigns, fulfilment, finance and operator tools in one platform.

    Can customers verify a Beaver draw?

    Yes. Beaver's current draw system publishes the information required for a player or other visitor to independently reproduce and check a result.

    Does Beaver work for licensed society lotteries?

    Yes, and here is the honest status: Built Lottery support is in the product, and no lottery is live on Beaver yet. The first lottery operator is preparing to launch. The operator holds the licence; Beaver provides the platform, and the same draw commitment, verification and audit machinery applies.

    Does Beaver support free entry routes?

    Yes. Beaver supports free entries from an online or postal route and allocates them into the same competition pool as paid entries.

    Does Beaver replace legal advice?

    No. Beaver can enforce configured platform controls and provides tools designed around relevant operating requirements. Operators remain responsible for understanding the legal and regulatory requirements that apply to their business.

    Can I export my customer data?

    Yes. The operator console can export players, orders, entries, draws and audit records.

    Can I move an existing competition business to Beaver?

    That is one of the use cases Beaver is being built for. Migration requirements depend on the structure and quality of the data held by the current platform, so existing operators should speak to us about what would need to move.

    Does Beaver have a mobile app?

    Native white label apps are on the product roadmap. They are not currently a live customer feature.

    Ready to build?

    Show us the competition business you want to run.

    We'll show you what Beaver can do today, what is built next and what still sits on the roadmap. No theatre. No mystery demo environment.

    See the product. Ask the awkward questions.

    Talk to the people who build it.