Why we built BYOK instead of becoming a sportsbook

The obvious way to build a betting product is also the wrong one for us: take deposits, show markets, run a wallet, and become the place where users bet. That path turns the product into a sportsbook or exchange. It also changes the company from an automation business into a custody, licensing, fraud, payments, and market-making business.

Glitch Edge is deliberately not that. We built around BYOK: bring your own key.

For launch, that means a user connects their own Cloudbet account by pasting an API key. Funds stay at Cloudbet. Withdrawals stay at Cloudbet. Glitch Edge stores the key encrypted, evaluates user-defined strategies, writes a ledger, and, when live mode is enabled, submits bets according to the user’s rules and caps.

That decision is not only technical. It is the product philosophy.

Custody changes everything

The second a platform accepts customer funds, it inherits a different job. Now uptime is not just about software reliability. It is about balances, withdrawals, fraud review, sanctions screening, chargebacks, wallet reconciliation, customer disputes, and jurisdiction-by-jurisdiction licensing.

Those are real businesses. They are not side quests.

A sportsbook should be excellent at risk, trading, payments, and compliance. An automation platform should be excellent at strategy configuration, evaluation, execution discipline, and auditability. Trying to be both at launch would make each worse.

BYOK lets Glitch Edge stay on the side of the boundary where we can create the most value. We automate rules against an account the user already controls. We do not become the account.

The user already has the opinion

The best early Glitch Edge user is not asking us what to bet. They already have a thesis:

• a league they follow closely,
• a market type they believe is slow to move,
• a price range they prefer,
• a staking rule they trust,
• and a sense that manual line-watching is wasting their time.

That user does not need another glossy sportsbook screen. They need a way to turn judgment into repeatable rules and then inspect whether those rules behave.

BYOK respects that. The platform does not pretend to be the source of edge. It gives the user’s strategy a controlled execution environment.

Security is smaller and clearer

A BYOK system still has security responsibilities. API keys are sensitive. They must be encrypted at rest, handled carefully in memory, and never printed to logs. The worker should write audit events for key access and bet attempts. Revocation should be obvious: if the user revokes the Cloudbet key, the automation loses access.

But that is a narrower problem than holding balances.

The right mental model is closer to a deployment key than a wallet. You are granting automation permission to operate an existing account under rules you set. That permission should be limited, observable, and removable.

It makes paper mode honest

BYOK also makes paper mode more meaningful. The same account connection that powers live mode can power live-odds paper mode. The strategy sees real markets, real timing, and realistic account context, but the worker writes simulated bets instead of sending orders.

That is better than a backtest pretending the market waited for you. Paper mode exposes practical problems: not enough qualifying markets, price movement between evaluation and action, caps triggering earlier than expected, or a strategy overfitting one sport.

The Free plan is intentionally built around this idea: one strategy, paper-only, full ledger. See the plan details on /pricing. If the paper ledger is not convincing, live mode should not be the next step.

Why Cloudbet first

Cloudbet is the launch sportsbook because it has a mature API and fits the self-serve automation pattern for many non-restricted markets. That does not mean Glitch Edge is permanently a Cloudbet-only company. The underlying engine is exchange-agnostic. Polymarket support is in preview as a read-only markets browser and wallet foundation, but the public narrative should stay honest: Cloudbet sports automation is the lead product today.

That honesty matters. A platform loses trust when it markets tomorrow’s roadmap as today’s working feature.

BYOK is not a loophole

BYOK does not remove the user’s legal obligations. Cloudbet has restricted jurisdictions. Users must follow Cloudbet’s terms and local law. Glitch Edge should never imply that Cloudbet automation is available in places where Cloudbet does not serve users.

The site now keeps the factual jurisdiction list in /legal/geo. Read it before assuming the product is available where you live.

The product we want

The best version of Glitch Edge is competent infrastructure for people who already know how they want to bet. It should make automation legible: what ran, what passed, what failed, what was capped, what settled, and what changed.

That is why BYOK is the right starting point. It keeps funds where they belong, keeps the platform honest about its role, and lets us spend engineering effort on the part users actually need: turning strategy into controlled automation.