01 / tapmi
tapmi
A production NFC identity product engineered by Reiwa Sakura Tech: physical cards and tags resolve over HTTPS to a private-by-tap profile. No app required for the recipient.
Live Explore tapmi →JAPAN × MYANMAR × GLOBAL
令和桜
Engineering the Next Generation
of Digital Societies
We design, build, and scale intelligent systems, from web and mobile platforms to AI, cloud, and enterprise solutions — with Japanese precision and a global vision.
▏ FEATURED PRODUCTS
Explore the products and engineering behind our work.
View all work ↗01 / TAPMI
tapmi is a production NFC identity product from Reiwa Sakura Tech. A physical card or tag resolves over HTTPS to a private-by-tap profile — no app required for the recipient.
Products
Tapmi, ShweTap, and LaBar — live systems, not decks.
01 / tapmi
A production NFC identity product engineered by Reiwa Sakura Tech: physical cards and tags resolve over HTTPS to a private-by-tap profile. No app required for the recipient.
Live Explore tapmi →02 / SHWETAP
An interactive product with guest play and optional account-linked progression. Live at shwetap.com.
Live Explore SHWETAP →03 / LABAR
A production mobility platform: Ride, Airport, Delivery, Schedule, Business, Driver, and Safety. Live at labartaxi.com.
Live Explore LABAR →SERVICES
Outcomes we deliver — not filler service names.
Production web apps that load fast, stay typed, and survive real traffic.
Native and cross-platform clients with a clear release and store path.
HTTP APIs with auth, validation, rate limits, and structured errors.
Repeatable deploys, containers, and infrastructure that can be rebuilt from config.
Bounded AI features with evaluation, not unbounded chat widgets.
Information architecture and UI that operators and customers can actually use.
Written boundaries for data, identity, and failure before implementation starts.
Threat-informed reviews, auth hardening, and public-safe disclosure.
Budgets for JS, images, and Core Web Vitals on the devices people use.
ENGINEERING
Least privilege, encrypted transport, scoped credentials, and reviewable change history before a system goes live.
Boundaries that can grow: APIs, data, and clients stay replaceable without rewriting the product.
Measure LCP, INP, and payload. Prefer static delivery and small client bundles over decoration.
Typed contracts, explicit ownership, and changes small enough to review.
Logs, health checks, and audit trails for the paths that take production traffic.
WCAG 2.2 AA targets: keyboard, labels, contrast, and reduced motion.
Scoped work, staging, handover, and a response target of one business day on new enquiries.
ARCHITECTURE
The public shape of a Reiwa Sakura system. Private hosts and credentials stay off this page.
Clients
What people touch
Application
Typed edges
Domain
Rules that outlive a UI
Data
System of record
Infrastructure
Rebuilt from config
The browser or app hits a public HTTPS host. Private addresses stay off the page.
The API checks the session, validates the body, and rate-limits before any write.
Domain rules commit to SQL. Cache and files can be rebuilt. The client never owns the truth.
PROCESS
A clear path so you always know what happens next.
A focused call on goals, constraints, and what already exists. We say if we are not the right fit.
Written deliverables, milestones, assumptions, and price before a line of production code.
Weekly visible progress — demos, reviews, and a single place to track decisions.
Source, docs, and a stabilization window. Support stays available when you need it.
PLATFORM
The same Chat, Meet, and GitLab stack we operate for delivery.
COMPANY
Engineers and builders shipping production software.
NEXT
Tell us about scope, constraints, and timeline. We reply within one business day.