About
What this blog is
Rebounder Tech Blog records what actually happened in production systems we run ourselves — backends on Google Cloud, digital signage on Android devices, PostgreSQL, and payments.
Every article is written by the people who operate the system in question.Incidents are published with the cause and the fix that stops them recurring. Writing only about what went well would make the posts worthless as engineering records.
We never write about customer information. No customer names, contract terms, or data from customer systems. The scope is infrastructure, devices, and implementation.
Company
| Name | Rebounder Inc. (株式会社Rebounder) |
| Address | 6-25-14 Hongo, Bunkyo-ku, Tokyo 113-0033, Japan |
| Representative | Kaito Okumura |
| Founded | February 2026 |
| Corporate number | 7010001263076 |
| Business | Software development using AI and DX |
| Contact | rebounder@googlegroups.com |
| Corporate site | rebounder.jp |
How these articles are written
- Every procedure, setting, and command comes from the record in the repository we actually operate. We do not write values we cannot back up.
- Each article lists the evidence behind it: which file, which line range, at which commit. The repositories are private, so we cannot link to them — but the pointer is recorded per article.
- When we cover a product or service, we also write what did not work.
- Some articles contain affiliate links. The content is not influenced by them. See the privacy policy.
- Articles reflect the state at the time of writing. Vendor behaviour changes; check the official documentation before acting.
Disclaimer
This blog is provided for information only. We make no warranty as to accuracy or completeness and accept no liability for damage arising from following what is written here. Verify in your own environment before applying anything to production.