Talk to us. Straight to the right inbox.
Sizing a larger workload, stuck on a running Cube, or working out whether Krova Cloud fits what you're building — here is the fastest route to an answer.
No sales call needed — Cubes from $2.92/moNo credit card to sign up
Pick the route that fits
Each of these lands somewhere different, and picking the right one saves a round trip. Some reach a mailbox; the rest answer the question outright, with nothing to wait for.
Sales & larger workloads
Planning a fleet of Cubes, one much bigger machine, or something with specific requirements? Send the shape and the workload and we will help you size it.
Product support
Account questions, billing, or something misbehaving on a running Cube. The support inbox goes straight to the team that operates the platform.
Security & disclosure
See exactly how per-cube isolation works, or report something you have found. Vulnerability reports go to the support inbox — the same address our security.txt publishes.
Developers & the API
Building on the API? The SDK, CLI, MCP server and REST API are documented and open-source — most integration questions are answered there before an email is needed.
Abuse, spam, phishing or copyright complaints about something we host have their own intake at report abuse, and formal legal notices go to [email protected].
Before you write
Most of what arrives has a faster answer elsewhere — and the rest gets one sooner when the first message carries the right detail.
Sizing something larger
Tiers lift automatically as you spend, so most people never need to ask. If you need headroom sooner — one much bigger Cube, or many at once — tell us the shape and the workload and we will review it. Limits are set per space, so we can raise yours without you changing plan or moving anything.
Checking it fits before you commit
You do not need to talk to anyone to try it. Signing up is free, and the platform is self-serve from there. If you would rather sanity-check an architecture first, send the shape of what you are building and we will tell you plainly whether a Cube is the right substrate — including when it is not.
Reporting a security issue
Send it to the support inbox — that is the address published in our /.well-known/security.txt per RFC 9116, and it reaches a real mailbox. Include enough detail to reproduce. We do not run a paid bounty, and we would rather say so than have you find out after the fact.
Something broken right now
Check the status page first — it is an external uptime monitor, so it is not us marking our own homework. If it is not platform-wide, support is the fastest route: include the Cube name or ID and roughly when it started, because the lifecycle log for that Cube is the first thing we read and a time window narrows it immediately.
Faster than an email thread
The places that answer most of what reaches the inbox, with nothing to wait for.
Documentation
Setup, the API, snapshots, custom domains and billing. Most of what reaches the inbox is already written down here.
Platform status
Uptime and incident history, published by an external monitor rather than by us — so it is not us marking our own homework.
Community Discord
Swap tips, ask questions and follow what is shipping, alongside other people running Cubes.
Pricing is published in full rather than quoted on request — every rate, tier and limit is on the pricing page, so you can work out the cost of your own workload without emailing anyone.
Or skip the email and run one
The quickest way to find out whether Krova Cloud fits is to launch a Cube and look at it. Signing up is free. Claim $5 in free credit — one-time, per account, and nothing is charged for it.