Choosing an integration
Hosted, your own front end, or a bespoke build.
The platform is the same in all three. Fans, quests, verification, rewards and the admin panel do not change. What changes is who owns the front end, and that decides how fast you launch and how far you can take the design.
Hosted app
We run the application and serve it on your domain, and you configure it in the admin panel so it looks like you: logo, cover art and per page background images, an accent colour that carries through the interface, fonts, corner radius and spacing, which features appear and in what order in the navigation, what each feature is called so quests can be missions, light or dark, and which languages are offered. The layout of a page and the shape of the components on it stay ours, and a design system that has to be matched exactly is what moves a partner to the next path. Configuration itself is days, two to four weeks once content, artwork and a launch plan are counted, and two to three months at larger organisations with legal review and custom onboarding screens. It suits a fan hub that is its own destination, run by a community team with no engineering time available.
Your own front end
You build the interface in your own codebase with the FanBase SDK and host it yourself. Two npm packages give you the API client, the quest state machine, the display strings and unstyled React components, so everything a fan sees lives in your own routes and components, rendered by your design system, with no FanBase stylesheet and no iframe. Verification, reward allocation and the rules about when a quest can be submitted stay on the platform, so you are not reimplementing whether someone really followed the account. A first build of sign-in, a quest list, a detail view and a claim is about a day of developer time, or roughly an hour if you hand the SDK's own prompts to a coding agent and review the diff. It suits engagement inside a site you already have, a campaign that should live on one page, or any team whose design system is not negotiable.
Everything technical is on FanBase SDK. Build it into your own site explains when to move and what carries over.
Bespoke build
We design and build the experience with you, on the same platform, with a team assigned to your account. It suits organisations with their own brand guidelines, procurement, accessibility requirements and a roadmap they want influence over. Talk to your FanBase contact before assuming this is the right path, because the two above cover most cases at a fraction of the effort.
Comparing them
| What changes | Hosted app | Your own front end | Bespoke build |
|---|---|---|---|
| Who writes the front end | Us | You | Us, with you |
| Engineering needed from you | None | A developer, briefly | None |
| Design control | Themeable | Total | Total |
| Time to first launch | Days to weeks, months with legal review | Hours to days | Weeks to months |
| Lives on your existing site | No | Yes | Either |
| Admin panel | Yes | Yes | Yes |
| Every feature available | Yes | The ones in the packages, see status | Yes |
Running more than one
Supported, and increasingly the normal answer. Keep the hosted app as the fan hub, and use the SDK to put three quests on a product launch page or a match centre.
Same community, same fans, one progress record. A fan who signs in on either surface is the same fan with the same points.
Widgets
Widgets are not part of the product. The SDK does the same job without a fixed appearance, and without putting an iframe between you and your fans.
If you are on an older agreement that mentions widgets, talk to your FanBase contact about moving to the SDK.