Who runs KoedoDB
KoedoDB is operated by RadarWorks LLC, located in Shinjuku-ku, Tokyo, Japan. We are a small team, and we operate the service ourselves.
KoedoDB was founded by Hisashi Ikari, who builds and runs the platform. He spent six years as a security and network administrator and several years as a Technical Account Manager at a security company, and about fifteen years running backend infrastructure at two game companies in Japan. He has written software for about as long — mostly PHP in the early years, Go and Python today — and has used Linux for over twenty years, since Debian 2.2 (“potato”).
He built KoedoDB because the hosting he used felt expensive for someone with many small ideas: roughly $25 a month for a BaaS plan and $20 for a PaaS plan, plus usage, for every app. At $7 a project, ten projects cost $70, and $140 with an app on each. You grow only the one that takes off. He admires Supabase’s libraries and the thinking behind them, and KoedoDB keeps them. They were just hard on his wallet.
Why the United States, and not Japan
We are based in Tokyo, but your project runs in the United States, as a rule on dedicated servers at OVHcloud. The reason is price. A server in Japan costs several times what a comparable one costs in the United States, and we could not keep a $7 plan at $7 on the servers we would need there. We chose to keep the price low and to ask you to accept the distance.
From Japan, a round trip to the United States takes roughly 200 ms. An app that makes many database calls in a row to draw one screen will feel it, so make fewer, larger queries. If that delay is not acceptable for what you build, KoedoDB may not be the right host for you today.
If enough of you ask for Japan, we will add it as an Area of its own, and it will cost more.
How we work
PostgreSQL runs as upstream publishes it. We do not fork or patch it.
We publish the middleware we use. As a rule, how we pin, build, and test the software KoedoDB runs is public on GitHub, so you can see what is running and how we check it.
We do not sell your data.
You can take your data and leave. Your database is plain PostgreSQL, and one standard command exports it, with your users. See Export.
Your project’s data lives in the Area you choose. As a rule it stays there. Today the Area is North America, on servers in the United States — not in Japan, even though we are based in Tokyo.
KoedoDB is an independent service. It is not affiliated with Supabase; “Supabase” belongs to its owner.
Built on open source
The software that serves your project is open source, and we run it as upstream publishes it. How we pin, build, and test each one is public on GitHub:
Around your project, the platform itself also stands on open source: Rauthy for signing in to the Console, and Harbor as the private registry for your images. We run them as their projects publish them.
The names belong to their owners. KoedoDB is not affiliated with them.
Built to be rebuilt
Our infrastructure is defined as code (Terraform and Ansible) and kept in version control, so a lost server is rebuilt from the repository, not from memory. The state of the platform itself is backed up off the servers, encrypted, and we practise restoring from those backups before we open sign-ups.
What a small team means
This is a small team rather than a company with a support tier chart. That is a real trade-off, and worth knowing before you pick a host: the people who run KoedoDB answer you directly, and there is no 24/7 on-call rota. During the beta we make no uptime or recovery-time commitment. Both facts are on this page on purpose.
When something breaks, we act at once. A security fix does not wait for a convenient hour: when an advisory concerns software we run, we update as soon as we can, outside the maintenance window if we have to, and write it down on Security updates.
Everything else waits for the maintenance window. Planned maintenance, including updates and restarts, is done Tuesday to Thursday, between 3:00 and 5:00 a.m. US Eastern time (midnight to 2:00 a.m. Pacific) — early morning in the United States. When it affects your project, we tell you three days ahead.
Where to find us
We are on X (@koedodb) and GitHub (KoedoDB). A support desk will be linked here when it opens.
For legal and privacy matters, see the Privacy Policy and the Terms; to report a vulnerability, see Security. What we updated after security advisories, and when, is on Security updates.