Civic and licensing platforms
Licensing, permitting, and enforcement systems for public-sector teams: applications, review workflows, approvals, and citizen-facing status.
gaijin designs, builds, and runs platforms for civic services, commerce, media, and the automation behind them.
外人 - outsider
End to end: scoping, design, build, deploy, and the operations that follow.
Licensing, permitting, and enforcement systems for public-sector teams: applications, review workflows, approvals, and citizen-facing status.
Seller onboarding, photo-first listings, catalogues, and the light administration that keeps a marketplace healthy.
Player and catalogue apps for phones, tablets, and TVs, with provider integrations and subtitles.
Push notification infrastructure and messaging integrations that reach people where they already are.
Bots, scheduled jobs, and monitors that quietly handle the recurring work: lookups, alerts, and reminders.
Cloud-first builds on edge platforms: databases, storage, deployments, and monitoring that stay cheap to run and easy to own.
Selected systems with client and product names withheld.
Civic
Application intake, officer review, approvals, renewals, and enforcement workflows for a municipal team, with mobile notifications keeping applicants and officers in step.
Web platform, .NET, mobile notifications
In daily production
Commerce
Seller onboarding, photo-first listings, browsing, moderation, and a light admin for a local marketplace that runs on edge infrastructure with no servers to babysit.
Next.js, Cloudflare Pages, D1, R2
Running on edge infrastructure
Media
A TV-first app for Android TV and mobile: catalogue browsing, playback, subtitles, and a pluggable provider system for content sources.
Android TV, mobile, provider addons
Shipped
Automation
Telegram bots and scheduled jobs that handle record lookups, monitors, and alerts, replacing recurring manual checks.
Telegram bots, scheduled jobs
Running daily
Direct lines. The people who scope your system are the people who build and run it. No relay layers, no lost context.
Boring where it counts. Proven tools and predictable infrastructure, chosen so the system is still maintainable years from now.
Small on purpose. A few projects at a time. Honest scopes, direct answers, and steady releases instead of a queue number.
Have a system in mind?