A database close to your users
An app hosted in Malaysia that talks to a database in Singapore, Tokyo or the United States pays for the distance on every query. HornetHive places your database in the region you choose when you create it, Malaysia today, with Singapore and Japan coming, so your app and its data can sit in the same country.
Each database is a real PostgreSQL 18 database with its own owner role. Nothing is emulated: with a direct connection string on the Pro plan, psql, pg_dump, Prisma, Drizzle, TypeORM, SQLAlchemy, Django, Laravel and Rails all connect as they would to your own server.
Managed for you
The parts of running Postgres that take time are done before you sign up:
- PgBouncer in transaction mode in front of every server, so serverless functions and busy apps do not run out of connections.
- TLS from your app to PgBouncer to Postgres, with a certificate from a public CA.
- One database and one role per customer; CONNECT is revoked from everyone else.
- Storage checked every ten minutes. Over the limit, databases pause instead of being deleted.
- Manual backups on every plan, downloaded as a .tar file you restore with pg_restore.
Paid the Malaysian way
Plans are priced in Ringgit and paid through Billplz with FPX online banking or a card. Paid plans are billed a year at a time with no auto-renewal, so nothing is charged without you choosing to renew. The free plan needs no card at all.
Starter is RM 7 a month for three databases and 5 GB; Pro is RM 29 a month for ten databases, 20 GB and direct connections. Both are billed yearly.
| Plan | Price (RM / month) | Billed | Databases | Storage | API calls / month | REST & GraphQL | MCP | Direct connection |
|---|---|---|---|---|---|---|---|---|
| Free | 0.00 | Free forever | 1 | 500 MB | 500K | Yes | — | — |
| Starter | 7.00 | Yearly, RM 84.00 | 3 | 5 GB | 2.5M | Yes | Yes | — |
| Pro | 29.00 | Yearly, RM 348.00 | 10 | 20 GB | 25M | Yes | Yes | Yes |
More than a connection string
Every database also gets a REST API for each table, a GraphQL API, and an MCP server for AI agents, all behind scoped API keys. Use the connection string from your backend on Pro, REST from your frontend, and let an agent read your schema over MCP: same data, same permissions.
Updated