GCP & Cloud Infrastructure
Infrastructure on GCP and AWS, defined in Terraform so that what is running can be read, reviewed and rebuilt.
Infrastructure that only exists as clicks in a console is infrastructure nobody can review and nobody can reproduce. Putting it in Terraform is not about the tool — it is about being able to answer “what is actually deployed, and who changed it?” without guessing.
The parts that tend to get skipped are the ones I start with: who can access what (IAM), where secrets live and who can read them, what the pipeline does before something reaches production, and what you will see when it breaks.
Typical engagements
- Moving existing infrastructure into Terraform without downtime
- Cloud Run, container build and deployment pipelines on GCP
- IAM review and secret handling with Secret Manager
- CI/CD pipelines, logging and monitoring for an existing system
Related work
- Dr.Well-B
Multi-service platform for doctors and dentists in Japan: verified membership with approvals, profile-targeted ads, dynamic surveys, job search and batch reward points.
- GO Inc
An ecosystem of 4 websites for the GO taxi brand — a 5-language product site, ATS-connected recruiting, a support center and corporate IR, with Slack-moderated publishing on Google Cloud + AWS.
- Wonderia
The multilingual brand website of Wonderia YOKOHAMA (wonderia.jp) — 4 languages, marketing self-publishing via Contentful, running serverless on Google Cloud.
- Yokohama Stadium
The official website of Yokohama Stadium (Hamasta) with a live play-by-play system — static-first on a CDN, event-driven serverless pipeline on Google Cloud and AWS.
- Corporate IR Platform
A corporate and IR website platform for a listed Japanese company — a fully self-built CMS, a Firestore-to-BigQuery data pipeline, and Google Cloud infrastructure behind a WAF.
- Beacon-based Content Delivery Platform
A multi-tenant BLE/iBeacon advertising platform that recorded 761,921 device connections in a single hour while matching campaigns and delivering context-aware content.
- How I Traced a Googlebot-only HTTP 500 Across Next.js, Cloud Run and the Hosting Edge
Users and every other crawler got 200 while Googlebot got 500 site-wide. The cause: a 404-path regression amplified by crawler verification at the hosting edge.
Technologies used in this work
- TypeScript
- BigQuery
- Cloud Run
- Docker
- Node.js
- Contentful
- Express
- Firebase Hosting
- Firestore
- Github Action
- Nuxt
- reCAPTCHA
- Cloud Storage
- Firebase Auth
- Gitleaks
- Next.js
Is this a fit?
- A good fit: business systems, backends and APIs, GCP and AWS infrastructure, production incidents.
- Not the right fit: work that is mainly pixel-perfect UI or heavy animation.
If this sounds like the problem you have, Send a project brief.
Your email app opens with a short brief to fill in.