The developer cloud
your AI can run.
Hosting, databases, storage, sign-in, email, payments, domains, AI models and agents. One account, one API key, and an AI connector that builds and runs all of it for you.
Free plan, no card needed. Add harakumo.com/mcp to Claude and ask.
Stop stitching. Start shipping.
A real app needs hosting, a database, files, sign-in, email, payments and AI. Bought from different vendors, that is seven bills, seven dashboards and seven ways to break. On Harakumo it is one account your AI can run end to end.
Stitching it together
7 vendorsShipping with Harakumo
1 platformAn illustration of a typical setup, not a measurement.
Everything your app needs.
One account.
Each service works today and sits behind the same key. Where something is missing, its docs say so. Not built yet: Postgres, social sign-in beyond Apple and Google, auto-deploy on git push, function logs, rate limits per site, and custom HTTP tools for agents.
Deploy
Static sites on the edge and Node.js apps in containers, at your-project.harakumo.app. Deploy from GitHub, a folder, the CLI or a chat; a failed build never replaces what is live.
Functions
One JavaScript file on the edge with its own URL and no server to size. Write it in the dashboard or send it from the API.
Domains
Search for a domain, pay from your balance and it connects itself, or bring one you already own. DNS editing, auto-renew and transfers included.
Shield
Block visitors from the countries you choose, addresses and ranges you list, and AI crawlers that say who they are; never serve the .env files, dotfiles or keys that sit beside your pages; put a static site behind a password; and see your workspace’s security checks in one place. HTTPS redirect and security headers on static sites, server apps, functions and worker.js programs, and network-level attack protection always on.
Repos
A code home inside Harakumo: numbered commits you can deploy, and roll back by deploying an older one.
const { deployment } = await hk.deployments.uploadDir(project.id, './dist');- deployment #41 · queued
- building…
- ready · https://my-store.harakumo.app
From one key
to a running product.
One example, a small online store, built up one family of services at a time.
Start with one key.
A workspace holds your projects, and one API key reaches every service in it. Create a project and it has a home.
const hk = new Harakumo({ apiKey });- hk_live_…
- Project · my-store
Put it online.
Deploy a folder or a repository and the project gets a real address. Each deployment moves through queued, building, deploying and ready, and a failed build never replaces what is live.
await hk.deployments.uploadDir(project.id, './dist');- Deploy
- Functions
- Domains
- Shield
- Repos
- ready · my-store.harakumo.app
Give it data.
The same client opens a SQL database, private file storage, vector search and memory for AI features.
await hk.databases.query(db, 'SELECT * FROM orders');- Databasesproducts and orders
- Storageproduct images
- Vector DBsearch
- Memorycarts
Open it to your users.
Sign a customer in, take a card payment and send the receipt: three calls from your app. Video and live channels sit in the same family.
await hk.payments.createSession(account.id, { amountCents: 2900 });- Authcustomer login
- Paymentscheckout
- Mailreceipts
- Media
And your AI can run it.
Your app calls 11 models through the same key. Claude gets its own door: add harakumo.com/mcp, sign in as yourself, and it can deploy, query and manage these same projects by being asked.
Add custom connector
https://harakumo.com/mcp- AI Gatewaysupport copilot
- Agents
- Claude · harakumo.com/mcp
- AI connector
Your cloud,
in the conversation.
Harakumo speaks the Model Context Protocol. Add one address to Claude, or any MCP client, and run the platform by asking.
https://harakumo.com/mcp- You sign in
- You choose the workspace
- Read-only, or allowed to change
- Your role, nothing more
Example conversation
- Deploy the latest commit of the store and tell me when it is live.
list_projectsfinds my-storedeploy_projectbuilds the latest commit from GitHubget_deploymentchecked until readybuildingdeployingready- my-store is live at https://my-store.harakumo.app
- Audit log ·
deployment.create· recorded under your name
Try asking
- Why did the last build fail?
list_deployments · get_deployment - How much of my plan is left this month?
get_usage - Buy fruitshop.com and point it at the store.
search_domains · buy_domain · connect_domain - Create an API key for the staging server.
create_api_key
What it changes in your setup, such as deployments, domains, keys and environment variables, lands in your audit log. Everyday calls, such as a query, an email or a checkout link, are counted as usage instead. You can disconnect it at any time. Tested with Claude.
Your AI builds it right.
The first time.
Every assistant connected to Harakumo follows one standard by default, so you stop asking for the same things on every project.
A tab icon, titles and link previews
Made first, on every page, so a shared link shows a proper card.
Every screen size, from the first build
Phone, tablet and desktop together. No asking for a mobile version.
Sign-in done properly
Full name, confirm password, the show/hide eye button, and a working password reset.
Lists that scale
Pagination, loading placeholders, and empty and error screens. Never a blank page.
The pages every app needs
Home, About, Contact, Privacy, Terms and a footer that links them.
An admin dashboard when it needs one
Users, orders and numbers to manage, checked on the server.
One professional look
One icon set, never emoji, and motion with a purpose.
The backend in one call
Database, storage, sign-in and keys created and wired, only what the app needs.
- Tab icon in every size
- Page titles and link preview
- Phone layout
- Privacy and Terms pages
- About and Contact linked
- Show/hide on every password field
- Unknown pages answer 404
All checks pass. Run after every deploy; anything missing comes back with its fix.
Your AI builds the app.
Agents run when called, scheduled or messaged.
Harakumo knows which agents a kind of app needs, and your AI can design any other. Every project draws its agents as a flow: what starts each one, what it does, and the services it uses. An agent runs when you or your app call it, from the dashboard, the API or the AI connector; on a schedule; when your app sends it a signed event; or when a visitor writes to it from your site, with read-only access to the project's own documents.
What starts it
Agents for a salon booking app
Services it uses
Booking assistant: Finds open slots, books the visit and confirms it by email. Starts: a customer asks for a time. Uses AI gateway, Database, Memory, Mail.
Reminder agent: Emails everyone booked for tomorrow a reminder with a link to reschedule. Starts: every day at 9:00. Uses AI gateway, Database, Mail.
No-show follow-up: Offers the customer the next open times. Starts: a booking is missed. Uses AI gateway, Database, Mail.
Weekly insights: Reports bookings, busy hours and no-shows to the owner. Starts: every monday. Uses AI gateway, Database, Mail.
A store gets a shopping assistant and a low-stock alert; a salon a booking assistant and reminders. Pick the ones you want and create them, up to 2 on Hobby.
Through the connector your AI creates, tests and improves any agent: create_agent, run_agent, update_agent.
Each run shows the tools it called, what came back and what it cost, paid from any AI your plan includes, then your balance.
Live in four commands.
Or none: connect your AI and ask it to build. Either way the free plan needs no card.
Needs Node 18 or later. Rather ask than type? Add the AI connector at https://harakumo.com/mcp.
One SDK for
the whole platform.
npm install @harakumo/sdk. The code below uses real calls; the output shows the shape of what comes back.
import Harakumo from '@harakumo/sdk';
const hk = new Harakumo({ apiKey: process.env.HARAKUMO_API_KEY });const { project } = await hk.projects.create({ name: 'my-store' });
let { deployment: d } = await hk.deployments.uploadDir(project.id, './dist');
// Poll until the build settles.
while (!['ready', 'failed'].includes(d.status)) {
await new Promise(r => setTimeout(r, 3000));
({ deployment: d } = await hk.deployments.get(d.id));
}
console.log(d.status, d.preview_url);→ project #12 · my-store→ deployment #41 · queued⧗ building…⧗ deploying…✓ ready https://my-store.harakumo.app
Your code, your users and your data, kept apart.
Every request is checked against your workspace and your role, so other customers can't read or change your projects, and the teammates you invite see only what their role allows.
Walled off from other customers
An API key belongs to one workspace. A session or AI connector acts for one person, only in the workspaces they are a member of, and a connector can be limited to just one. No one else’s can read or change your code, databases, files or users.
Your own database, your own storage
Each database is a separate database and each bucket a separate bucket. Files stay private, behind links that expire after 15 minutes unless you choose longer.
Passwords and keys kept as hashes
Your password and your app users’ passwords are stored only as salted hashes. API keys and tokens are stored as hashes, and a new key is shown to you once.
Secrets out of sight
Viewers and read-only keys never see your environment variable values, the AI connector never returns them, and your static site never serves .env files or private keys.
Card numbers never touch us
Buyers pay on a hosted checkout page, so card numbers never reach Harakumo or your app.
Not sold, not trained on
We don’t sell your data or train AI models on your code or stored content, and harakumo.com runs no ad trackers.
Our admin tools are on the record. No one at Harakumo can sign in as you. Our staff need two-factor sign-in for every page and action in our admin tools, and opening your workspace there, or changing anything in it, shows in your audit log.
One plan for several workspaces.
Every limit in plain sight.
Each number is the one the platform enforces. Anything we do not measure yet is labelled that way, not sold as a quota.
Hobby
free limits per person
For trying Harakumo and personal projects.
- Apps and sites (projects)
- 3
- Server apps (Node.js)
- Pro and up
- Databases
- 1 · 0.5 GB in all
- Storage buckets (files)
- 2 · 1 GB of files
- AI usage
- Pay as you go from your balance
- Team members
- 3
Pro
covers up to 3 workspaces
For launching a real app with a small team.
- Apps and sites (projects)
- 20
- Server apps (Node.js)
- Included
- Databases
- 10 · 5 GB in all
- Storage buckets (files)
- 20 · 50 GB of files
- AI usage
- Pay as you go from your balance
- Team members
- 10
Team
covers up to 10 workspaces
For a team running several apps or clients, with a monthly usage credit.
- Apps and sites (projects)
- 100
- Server apps (Node.js)
- Included
- Databases
- 50 · 25 GB in all
- Storage buckets (files)
- 100 · 250 GB of files
- AI usage
- Pay as you go from your balance
- Team members
- 25
Scale
covers up to 25 workspaces
For many apps and clients, with the highest limits sold online.
- Apps and sites (projects)
- 500
- Server apps (Node.js)
- Included
- Databases
- 100 · 100 GB in all
- Storage buckets (files)
- 500 · 1,000 GB of files
- AI usage
- Pay as you go from your balance
- Team members
- 100
Free limits are per person, across all your free workspaces. A paid plan's limits are shared across the workspaces it covers.
Enterprise
For companies that need more than Scale, arranged with us rather than bought online.
- Limits and the number of workspaces covered, set for what you run
- Help moving your apps and data onto Harakumo
- Talk directly with the team that builds it
- Workspaces already on Enterprise keep it, at the price they pay
Prices are in US dollars and do not include taxes such as sales tax, VAT or GST.
Selling with Payments
3.9% + 30¢ per successful charge, with no monthly fee. On a $29.00 sale you keep $27.57. Earnings are held 7 days before you can withdraw them.
Beyond your plan
Plan limits answer HTTP 402 and rate limits 429, each naming the limit. File storage, database storage and build minutes stop at the limit on Hobby; on Pro, Team and Scale they keep going, paid from your prepaid balance. Server-app awake time on Pro, Team and Scale is paid the same way, at $0.05 per awake hour. AI past any included amount (Enterprise, or a Pro subscription from before these plans) and every domain are paid from the balance. No surprise bills: when the balance is empty or your spending limit is reached, the call is refused.
Build something real today.
Start free with no card. Connect your AI and ask it to build, or deploy a folder yourself.
- One account, one API key
- Sites, apps and functions on the edge
- Network attack protection on every site
- SQL databases and private storage
- Sign-in, email and payments built in
- Every major AI model behind one key
- Agents your AI designs for you
- A build standard your AI follows
- Every limit published
- Free plan, no card needed