Craftsmanship
Monozukuri applied to software: reviewed, tested, and built to last.
Technology Reliability Opportunity
Software built in Japan for companies around the world.
Petalxtech is a small engineering company in Tsuwano, Shimane. Development, cloud, web and mobile, AI and data. Technology is not one part of what we do, it is all of it. Tell us what you are building, and you will be talking to the engineer who would build it.
- Full-stack
- web, cloud, AI, data
- Worldwide
- where our clients are
Strategy
Five strategies, one blossom
The sakura is our symbol. It opens with five petals, and so does the way we work: five strategies that carry equal weight, none of which stands without the other four.
Global Reach
Built in Japan, delivered wherever you are, in English throughout.
Technology
A modern stack chosen for fit, not fashion. AI where it earns its place.
Trust
Partnership over ticket-taking: the same engineers, telling you the truth.
People
We hire engineers anywhere in the world. What decides it is the work, not the address.
01 · What we do
Technology-led work, across six practices
Most clients begin with one of these and grow into the others. The same team carries the work across all six.
Software Development
Custom systems, from greenfield builds to modernising code that has been running for a decade.
- Backend
- APIs
- Legacy
Cloud & Infrastructure
Design, migration and day-two operations on AWS, Azure and Google Cloud.
- AWS
- Kubernetes
- IaC
Web & Mobile
Interfaces your customers actually use: accessible, fast, and tested on real devices.
- React
- iOS
- Android
AI & Data
LLM and data systems grounded in your own corpus, with retrieval and evaluation you can audit.
- LLM
- RAG
- Analytics
IT Consulting
An outside read on the system you have: what to keep, what to replace, and what it will cost either way.
- Architecture
- Audit
- Roadmap
Business Automation
The repetitive middle of an operation, handed to software so your people can do the part that needs judgement.
- Workflow
- Integration
- Reporting
02 · Why us
Why work with Petalxtech?
Not a vendor you brief and forget. A team that stays with the system it built, and tells you the truth about it.
Small by design
Staying small is what lets the person who designed your system still be the person answering questions about it three years later. You will know our names, and we will know your codebase.
English, end to end
Calls, documents, code review and commit messages: all of it in English, by the same engineers who write the code. Nothing is lost on the way to us, and nothing needs translating on the way back.
Prevention, not triage
We treat a defect as something to prevent rather than something to catch. It costs a little more in the first month and a great deal less every year after, the part most vendors never have to live with, because they are gone by then.
03 · Approach
Substance over noise
Three steps, no theatre. You see something real early, and you always know what it cost.
-
1
Understand the system you have
Before proposing anything we read the code and talk to the people running it. You get a straight account of what to keep, what to replace, and what each will cost, including when the honest answer is that you need less than you thought.
-
2
Build the smallest thing that works
Shipped and running beats designed and pending. We put something real in front of you early, watch how it behaves with your data and your people, and grow it from there.
-
3
Stay after launch
Day two is the part most vendors leave. Operating what we built is how we find out whether we built it properly, and it is where a system either earns its keep or quietly starts costing you.
04 · Stack
The tools we reach for
Chosen because they are well understood, not because they are new. If what you run is not on this list, say so anyway: most of our work begins inside somebody else's codebase.
Build
- Backend
- APIs
- Legacy systems
Run
- AWS
- Kubernetes
- IaC
Interface
- React
- iOS
- Android
Intelligence
- LLM
- RAG
- Analytics
05 · Company
A team hired anywhere, building for clients everywhere
We began with servers, code, and the ordinary work of keeping systems running. That is still exactly what we do. What we added was the other half of the problem: companies on the far side of the world who need software built properly, and a team that builds it that way.
Our clients are in the United States and beyond. Our engineers are wherever we find them: the company is rooted in Tsuwano, Shimane, and the team is not limited to it. What holds the work together is a shared working language, and a way of building that treats a defect as something to prevent rather than triage.
We are a small company by design, and we are taking on new clients. If you have a system that needs building, rebuilding, or simply keeping alive, we would like to hear about it.
06 · FAQ
Questions, answered straight
What people ask us before the first call.
How do we start working together?
Send the problem through the form, or take a thirty-minute slot in the calendar, whichever suits you. The first conversation is with an engineer rather than a salesperson, and its only purpose is to work out whether we are the right people for the job. If we are not, we will say so.
Can you work alongside our existing engineering team?
Yes, and often that is the better shape. We join your repositories, your review process and your standups, and work as part of the team rather than a separate island that hands over a zip file at the end.
Can the whole engagement run in English?
Yes. Calls, documentation, code review and commit messages are all in English, handled by the engineers doing the work rather than by an account manager relaying messages.
Contact
Tell us what you are building
Send us the problem, or take a slot in the calendar. Either way the first conversation is with an engineer rather than a salesperson.
Send us a message
We reply to every enquiry within one business day.
- Location
- Tsuwano, Shimane, Japan
- Response
- Within one business day
- Languages
- English / 日本語
Thank you. Your message is with us
We will reply within one Japanese business day. If it is urgent, say so in a follow-up and we will move it up the queue.
Rather talk it through?
Take a thirty-minute slot in our calendar. The call is with an engineer.