Skip to content
Docs · Start here

Architecture

How the pieces fit: your app on the edge, and every capability it needs — data, files, search, sessions, sign-in, checkout, email, AI — one call away on the same key.

View as Markdown
All topics

Harakumo is an app's whole backend behind one client. Your front end and server deploy to the Harakumo edge; every capability the app needs is a namespace on the same SDK or a path on the same API, already wired together. The diagram shows a real shape — an online store, end to end — with the role each service plays.

Your server holds the API key; browsers get only what your server hands them (signed upload and download URLs, checkout links) or the auth pool's publishable client id.

usersyour appfrontend + server · deployed from Git or an uploadmy-store.harakumo.appliveconst hk = new Harakumo({ apiKey })Databasesproducts & ordershk.databasesStorageproduct imageshk.storageAuthcustomer login · JWThk.authPaymentscheckout & payoutshk.paymentsVector DBsemantic searchhk.vectorsMemorycarts & sessionshk.memoryAI Gatewaysupport copilothk.aiMailorder receiptshk.mailevery arrow is one SDK call — no service accounts, no glue infrastructure