X65 Studio · Taipei · Available for projects

Exactly whatyou want

We design and build the software small businesses run on — websites, internal tools, apps for phones and tablets, smart TV apps, and the other systems that keep operations moving.

02 · Proof

Clinics running software we built, every day
400+
Years of engineering experience behind the work
10+
Systems taken from nothing to production
4
Working days to a reply, every enquiry
2

03 · Services

Custom internal tools

The thing your team currently does in a spreadsheet, a group chat, or on paper. We turn it into software that fits how they already work.

  • A working tool your staff can use on day one
  • Whatever data it needs pulled from the systems you already run
  • Documentation written for the people using it

Flutter · REST & WebSocket APIs · SQL · Firebase

Apps for phones, tablets and screens

One app that runs everywhere your business needs it — a phone in someone's pocket, a tablet on the counter, a screen on the wall.

  • iOS, Android, tablet and web from a single codebase
  • Offline handling, so a dropped connection is not an outage
  • One-button releases, so every device stays on the same version

Flutter · Melos monorepo · Hive offline cache · CI/CD

Websites with an admin you own

A public site, plus the admin your own staff use to change it. Saving publishes — no engineer in the path.

  • News, case pages and locations each maintained in-house
  • Images uploaded by dragging them in, hosted off your web server
  • Pages generated ahead of time, rebuilt when content changes

Next.js · React · Tailwind CSS · content admin · Cloudflare R2 · ISR

Back ends and cloud

The layer holding an app up: APIs, databases, live connections, and wherever those actually run.

  • APIs and databases designed from scratch, or an existing one taken over
  • Live push, so one change reaches every device at once
  • Containerised deployment, with errors and performance watched

Fastify · ASP.NET C# · Rust · Go · PostgreSQL · Redis · WebSocket · GCP Cloud Run · Docker · Sentry

Automation and AI

Repetitive, time-consuming work is automated while the judgement calls stay with a person. Anything that calls a model runs under a spending cap.

  • The repetitive steps handled automatically
  • A spending cap, so costs stay predictable
  • A full record of what ran, open to audit

Node.js · Claude API · structured output · cost guardrails

04 · Work

04 · Work — 01

Waiting-room screens for 400+ clinics

Calling the next patient meant a nurse leaving the consulting room to say the name across the waiting area. Clinics with a ticket display had the number and nothing else, and notices still went up on paper.

The display combines queue calling, health video playback and digital notices. The number comes from either the clinic's third-party HIS or our own admin, and pushes to the dispenser, the wall screen and the ticker at once. The current number is also published online.

Clinics running it every day
400+
Kinds of floor hardware on one live connection
3
Trigger releases both apps to every site
1

Flutter · Melos monorepo · Fastify · React admin · PostgreSQL · Redis · WebSocket · Hive offline cache · HIS integration · GCP Cloud Run · CI/CD

Read the full case →

04 · Work — 02

Crash triage that replaced a paid subscription

A system running across hundreds of sites produced more crash reports than anyone could read, and sorting them by hand cost a morning. The paid tool that summarised them billed for everything it read, and the bill grew with the site count.

The triage tool filters device and network noise with plain rules first, then sends only the plausibly fixable bugs to a model, under a spending cap and behind a fingerprint cache so the same crash is never paid for twice. It is open source and runs against the 400-site system.

Of 148 reports filtered before anyone read them
64
Real bugs discarded by mistake
0

Node.js · SQLite · Sentry API · structured LLM output · cost guardrails

Read the full case →

04 · Work — 03

A distributor's site, maintained in-house

A corporate site for the distributor of an international simulator brand. It carries four kinds of content — the brand, client stories, news and dealer locations — and the last two keep moving.

The public site and the admin were built as one job. The site renders through ISR, so it loads at static speed and still reflects current content; the admin is a full content system with a rich text editor, image uploads and create-edit-delete screens for every resource. Images are hosted on Cloudflare R2, the admin is protected by NextAuth, and every API route that writes verifies a JWT.

Deploys needed for a content change
0
Kinds of content with their own admin
4

Next.js · React · Tailwind CSS · Prisma · Neon · NextAuth · Cloudflare R2 · ISR

Read the full case →

04 · Work — 04

Photograph a note, get cards that arrive as you forget

A vocabulary app, built for the words you learn and then forget.

Photograph a page and AI turns the notes into flashcards in seconds. SM-2 spaced repetition puts a card in front of you at the moment you are about to forget it, so what you learned makes it into long-term memory. Local-first and usable offline, syncing across devices once you sign in, with ready-made decks in the marketplace. It is on the App Store.

Bars of signal needed to review
0
Interval algorithm timing every card
SM-2

Flutter · Riverpod · Cloudflare Workers · D1 · R2

Read the full case →

05 · Process

  1. 01

    A first call to define the problem

    The first call establishes the scope of the problem, its size, and how we would solve it. Meetings are arranged in your timezone. You get a dedicated point of contact.

  2. 02

    You get the scope in writing before anyone codes

    Before any work starts we put what is being built, what is not, and what it costs into a document you approve. The quote and the final acceptance both follow it.

  3. 03

    Progress you can check any time

    You get a private link at the start of the project showing the stages, where we are, and every update as it happens — no login needed. Each stage also ends with a written report. Stages run from one week to three.

  4. 04

    You pay per milestone

    The project is split into milestones with a visible result, each invoiced on delivery through Wise. You can stop at the end of any stage and keep what you have paid for.

  5. 05

    The code is yours at handover

    Source code and intellectual property transfer to you on final payment. Delivery includes the repository, the deployment setup and documentation, so the work can change hands at any point. If you would rather we kept looking after it, maintenance and hosting are available separately.

06 · FAQ

  • Meetings are arranged in your timezone. Messages are answered within two working days.

  • After the first call we put the scope in writing: what is being built, what is not, and where the variables are. The quote follows that document and is priced by milestone. Where the scope is still unclear, we propose a paid assessment first.

  • By milestone, through Wise, invoiced as each one is delivered. A project is usually three to five milestones. W-9 available for US clients.

  • Adjustments within the agreed scope are not billed separately. Where a request changes what is being built, we set out the effect on time and cost, and start once you approve it.

  • Yes. Send yours over and we will review it and sign. Tell us at the start if the project should stay out of our work section.

  • Everything transfers to you on final payment, source code and intellectual property, with no licence retained. General-purpose open-source tooling that predates the project is the exception and keeps its own licence.

  • We can stay on for maintenance — fixes, small changes, dependency and platform updates — billed separately, either monthly or per request. You can also just call us when something comes up. Server setup and hosting on Google Cloud is available the same way, or you can keep it with your own team.

07 · Contact

Tell us about your project

Tell us what you want built, or where things are stuck. We reply within two working days.

Images or PDF — up to 3 files, 5 MB each.