Independent software studio
An independent software studio that builds its own products and selectively takes on commissioned work. Based in Japan. Direct correspondence in Japanese and English; other languages handled via translation tools.
About
The name HeliFraxis is built from three roots: Helix, Frakt, and sis. Each one points to something the studio holds close.
Helix
Helix in motion.
A word for the underlying structure of software. As a project grows, its shape inevitably shifts, and the studio keeps a careful eye on designs that remain stable as additions accumulate. The way the foundation is laid often decides whether something can ship at all.
Frakt
Frakt happens.
A word for friction with reality. Every product runs into the unexpected sooner or later. People use what we make in ways we did not foresee, and plans rarely survive contact with the world untouched. Rather than turn away from those rough edges, the studio takes them as a sign of where the real work lies.
sis
Praxis ships.
A word for practice — for the act of making things. Theory and discussion matter, but there are things that only become clear once a piece of software has been written and run. What surfaces only after release, in the hands of those who use it, is what the studio values most.
Products
These are the products the studio builds and runs. Because the number we can attend to at the same time has its limits, the lineup is kept deliberately small.
Services
Outside commissions are taken on in small numbers, depending on what the studio can give them. The judgment turns on whether the studio can engage with the work with the same attention it gives its own products. Where that seems unlikely, the studio declines, for the requester's sake as much as its own.
Product build
A requested product or feature, taken end to end — design, implementation, release, and refinement. AI work centres on integrating existing models — Claude, GPT, and the like — into a product, rather than training or operating models from scratch. A natural fit for teams whose technical organisation is still forming, or where hiring a technical lead in-house remains difficult for the moment.
Web applications, mobile apps (iOS / Android), APIs and backends, database design, AI / LLM integration, realtime communication, data pipelines, automation scripts, and the like.
Systems & integrations
Connecting the systems that ought to be connected: internal tooling, AI workflows, data pipelines. Often arises in the course of a product build.
Internal tooling, AI workflows, data integration, API integration, authentication and payments, webhooks, third-party service integration, data migration, and the like.
Technical advisory
An ongoing conversation around technical decisions. Architecture review, hiring, AI strategy — for moments when one more perspective would help before a call is made.
Architecture review, AI strategy, technology selection, second opinions on high-stakes decisions, and the like.
Branding & logos
Logos, simple brand guidelines, and web-facing assets for small operators. AI tools are part of the toolkit, used measuredly to arrive at something the client can stand behind.
Logos, brand guidelines, 3D assets, web-facing visuals, social media assets, print design, and the like.
Japanese ↔ English translation
Translation between Japanese and English. The studio works carefully with the source's intent and register, aiming at a translation that reads naturally rather than one that merely substitutes words. Suitable for both technical and business writing.
Technical documentation, websites, contracts, product copy, email correspondence, press releases, UI text, and the like.
Because the work and difficulty differ from project to project, fees are not given as a fixed range. After hearing the requirements, the studio returns an estimate. Inquiries outside the examples above are still welcome — depending on the substance, the studio may well take them on, so please feel free to write in.
How it goes
Initial inquiry
A short note will do — what is being attempted, what currently stands in the way, and the date if there is one in mind. The form is open; please write in whatever way is comfortable.
Scoping
A short call to confirm that the request and what the studio can offer are aligned. If they are, the studio returns scope, schedule, and an estimate in writing within a few days.
Build
Work proceeds in short cycles. A staging link and a weekly note keep the progress visible, so the work never disappears into a black box between updates.
Handover & ongoing support
On completion, the studio offers either a handover of code, documentation, and deployment, or continued operation under the studio's care — whichever serves the project best. Support continues for a period after release, so the relationship does not simply end with the invoice.
Contact
Commissions, partnerships, anything that does not fit in a few lines — email is the surest way in. Every message is read in full. Replies typically follow within one business week.
Replies typically follow within one business week.
Direct correspondence is in Japanese and English. Other languages can be handled with the help of translation tools — please feel free to write in whichever language is comfortable.
New inquiries are being received at the usual pace.