Agave
Problem
A Japanese plant retailer needed the whole commerce path — catalogue, order management, payment — on the payment rails Japanese buyers already use.
Approach
Owned the platform end to end with a team of 5 — product through order management, GMO Payment Gateway for payments, a Laravel admin portal, and the AWS environment underneath.
Outcome
Delivered on schedule with a team of 5
A plant e-commerce platform for the Japanese market, owned end to end with a team of five: product catalogue, order management, and payment through the GMO Payment Gateway that Japanese buyers expect. The admin portal is Laravel. I owned the AWS environment as well — ALB, EC2, RDS, S3, Route53 — with Kubernetes orchestrating the development tier. The client was exacting and the delivery date held.
What I did
- Ran a plant e-commerce platform for the Japanese market with full end-to-end ownership of a 5-person team — product catalogue through order management, with the GMO Payment Gateway carrying payment.
- Owned the AWS environment — ALB, RDS, EC2 and S3 — built the admin portal in Laravel, and delivered a demanding Japanese client on schedule.
- Ran Kubernetes for development-server orchestration.
Stack
Screens
More work
SystemsSource?. Manga
A digital manga and video streaming platform.
SystemsRyobi
Concurrent Japanese enterprise projects — city council services, agri-business portals, milk collection and distribution, and hospital management.
SystemsPaperless
A payment gateway for Paperless Limited.
Building something that needs this kind of engineer?
Hiring, contract, or an architecture problem — tell me the shape of it and I’ll come back with something specific.