The Bkper Platform

The Bkper Platform is a complete managed environment for building, deploying, and hosting apps on Bkper. It removes infrastructure complexity so you can focus on business logic.

What the platform provides

Hosting

Apps are deployed to {appId}.bkper.app on a global edge network powered by Cloudflare Workers for Platforms. Your app runs close to your users, with zero infrastructure to manage.

Preview environments are built in — deploy to a preview URL to test before going to production.

Authentication

OAuth is pre-configured. No client IDs, no redirect URIs, no consent screens to build. In your client code, call auth.getAccessToken() and the platform handles the rest. In your event handlers, the user’s OAuth token arrives automatically in the request headers.

Services

Declare the services you need in bkper.yaml and the platform provisions them:

• KV storage — Key-value storage for caching and state. Access via c.env.KV in your handlers.
• Secrets — Securely stored environment variables. Set via bkper app secrets put, access via c.env.SECRET_NAME.

Developer experience

One command starts everything:

bkper app dev

This launches the Vite dev server (HMR for your UI), the Workers runtime (for your server and event handlers), and a Cloudflare tunnel (so Bkper can route webhook events to your laptop). Your entire development environment, running locally.

Deployment

Two commands to go from code to production:

bkper app sync && bkper app deploy

Your app is live at {appId}.bkper.app. The platform handles routing, SSL, and edge distribution.

What you’d build yourself without it

Without the platform, creating a Bkper app with a UI, event handling, and authentication requires:

Concern	Without the platform	With the platform
Hosting	Provision servers, configure domains, SSL, CDN	bkper app deploy
Authentication	Register OAuth client, build consent screen, handle token refresh, manage redirect URIs	auth.getAccessToken()
Event webhooks	Set up a public endpoint, configure DNS, handle JWT verification	Declare in bkper.yaml, platform routes events
Local dev webhooks	Install ngrok or similar, manually configure tunnel URL	bkper app dev starts tunnel automatically
Secrets	Set up a secrets manager, configure access	bkper app secrets put
KV storage	Deploy Redis/Memcached, manage connections	Declare KV in bkper.yaml
Preview environments	Build a staging pipeline	bkper app deploy --preview
Type safety	Manually create type definitions	env.d.ts auto-generated

The platform eliminates all of this. You write business logic, the platform handles infrastructure.

Getting started

# Create a new app from the template
bkper app init my-app

# Start developing
bkper app dev

This gives you a working app with a client UI, server API, and event handler — all running locally with full HMR and webhook tunneling.

See Your First App for a complete walkthrough, or continue to App Architecture to understand how platform apps are structured.