Company
Poocraft is a B2B technology provider for iGaming. Our work is the platform underneath casino and sportsbook brands. The brands, the licences and the players belong to the operators.
- What we are
- A technology provider for casino and sportsbook operations
- Who we work with
- Licensed operators and businesses preparing for a licence
- What we never do
- Operate gambling services or accept players
01Positioning
Poocraft builds and maintains the software that licensed casino and sportsbook brands run on: the operator console, game aggregation, the sportsbook integration layer, the wallet, analytics, and the APIs that connect them.
We are not a casino and we are not a bookmaker. We do not take bets, we do not register players and we do not hold a gambling licence on anyone's behalf. Those belong to the operators we work with, and we keep the line between the two roles deliberately sharp.
That separation is useful to operators. A provider that does not compete with its customers can be judged on one thing: whether the technology does what it says.
Every page of this website is written for operators and their teams. Nothing on it is an invitation to gamble.
02Engineering principles
Six principles that show up in the product, in the documentation and in the way we work with operators.
Contracts before features
Every module and every adapter has an explicit contract. We would rather publish a small contract we can keep than a large one we cannot.
In practiceNew connections reuse a category contract instead of adding special cases.
Money is handled once
Anything that moves value is idempotent, double-entry and reconcilable. A duplicated transaction is a design failure, not an operational incident.
In practiceWallet writes require an idempotency key.
Operators hold the controls
Decisions that belong to the operator are settings in the operator's console, protected by roles. They are not tickets in our backlog.
In practiceLimits, markets, margins and roles are configuration.
Honest previews
What we show before a contract is either the product running on generated data or clearly marked as illustrative. We do not publish numbers we cannot document.
In practiceEvery preview on this site carries a sample or sandbox label.
Predictable where it matters
For the ledger, the audit log and the API we choose well-understood designs, and keep experiments for places where a mistake is cheap.
In practiceWithin an API version, only backwards-compatible changes.
No lock-in by obscurity
Documented APIs and exportable data mean an operator can extend the platform, or replace a part of it, without asking us first.
In practiceThe console uses the same API as your developers.
03How engagements run
Every engagement follows the same shape. What changes is the scope, and that is agreed in writing before work starts.
01
Discovery
We map your markets, licences, products and existing systems, and agree scope, responsibilities and a realistic plan.
Who is involved
Your product, compliance and technical leads, with our engineers
02
Configuration
Your tenant is set up: brands, roles, currencies, limits and jurisdiction rules. The front end is themed or connected.
Who is involved
Your operations team and designer, with our onboarding team
03
Integration and testing
Providers, payments and compliance services are connected and tested end to end in the sandbox before any real traffic.
Who is involved
Your developers and providers, with our engineers
04
Launch and support
Go-live follows a readiness review. Afterwards you have monitoring, runbooks and a direct line to engineers.
Who is involved
Your operations and support teams, with our engineers
Timelines depend on your markets, your licences and the number of integrations. We give a plan after discovery, not before it.
04What we don't do
Knowing what a provider will not do is as useful as knowing what it will.
Questions about how we work? Write to [email protected].
We do not operate gambling services
Poocraft does not run a casino or a sportsbook and has no players of its own.
We do not accept players or hold their funds
Player accounts and balances belong to the operator. Payments run through the operator's own providers.
We do not supply licences
Each operator holds its own licence for each market. We provide the technical documentation a licensing process asks for.
We do not set odds
Prices and results come from the sportsbook service the operator contracts. We provide the integration and the controls.
We do not give legal or regulatory advice
We work alongside your compliance team and your counsel. They decide what the rules require.
We do not publish claims we cannot document
No invented metrics, customer names or certifications. Evidence is shared in context, under an agreement.
Work with us
Tell us about your operation and your plans. We will answer with specifics, not a brochure.