FAQ
Frequently asked questions about Kisenon.
Is Kisenon a fork of Neon?
Kisenon uses Neon's open-source storage and compute components. The control plane, scheduling, billing, and operational tooling are re-implemented in Go for our deployment model. Wire-compatible with upstream Neon clients where applicable.
What region is data stored in?
Today Kisenon runs out of a single home-cluster region (US, on bare metal). Multi-region lands when there's customer demand for it.
Is there a free tier?
Yes — alpha access is free. Long-term pricing will be storage-only with no compute floor. See Alpha access.
How does scale-to-zero affect my application?
Idle endpoints suspend after 5 minutes. The next packet wakes them in typically under 500 ms — fast enough that ORMs do not see a timeout.
If your workload is latency-sensitive on cold starts, you can keep an
endpoint warm with a periodic SELECT 1.
Can I use my existing Postgres tooling?
Yes. Kisenon speaks vanilla Postgres wire protocol. Anything that
talks to Postgres works: psql, pg_dump, drivers, Drizzle, Prisma,
SQLAlchemy, etc.
Where do I report bugs?
During alpha, file issues at github.com/Seiraiyu/Kisenon or reply to your alpha welcome email.
Where do I report security issues?
See /.well-known/security.txt for the disclosure contact.
Is there a CLI?
Yes — see CLI. Install via curl ... | bash (mac/Linux)
or iwr ... | iex (Windows PowerShell).