Japan · Async only
Available for subcontract work

Fixed-scope development, delivered asynchronously.

Desiria LLC is a Japan-based software company. We take overflow and fixed-scope work from agencies and product teams — written specs in, working software out. No calls, no on-site, no on-call rotations.

01

What we build

This is what we take on, not a list of things we've shipped for clients — we're new and we'd rather you knew which is which. The part you can verify today is the data-integration work, linked further down.

Applications
  • TypeScript, React, Next.js, Node.js
  • Python services and tooling
  • WordPress & Shopify — themes, plugins, apps
AI & automation
  • RAG and document processing pipelines
  • LLM features — classification, retrieval, structured extraction
  • REST/GraphQL integrations, ETL, scheduled jobs
  • Internal tools and workflow automation
02

How we work

Asynchronous by default

Email, Slack, or your issue tracker. We won't ask you for meetings. Specs come to us in writing; status goes back in writing.

24-hour first reply

That's what we aim for, weekends included, and we'll say so if we're going to miss it. We're in the Japan time zone, so in practice work lands while your team is asleep.

However you contract

Hourly, day rate or fixed scope — whichever your team already uses. What we can't do is on-site, on-call, or meetings.

AI-built, disclosed up front

Development is carried out by an AI agent under the owner's direction, not by AI tools bolted onto a human workflow. We say so before you commit, because some end clients restrict it. Responsibility, confidentiality and IP assignment sit with the company either way.

03

Working with us the first time

We're a new company, so we don't have a portfolio we're allowed to show you. We'd rather say that plainly than pad a page with logos.

So here's the offer for a first engagement: give us something small and low-risk and we'll do it at no charge. No strings — if you don't like the result, that's the end of it and you owe us nothing. What it does cost you is real — your time briefing us, and whatever you had to share to make the work possible — so keep the first one genuinely small: a bug, a migration script, one endpoint. If unpaid work is awkward for your side, a paid test task is equally fine and we'd rather you said so than walked away.

What we can point at instead is work you can open and run yourself — for example an OpenFn data-integration example, published with a test suite that runs against a real PostgreSQL. Read the code, run the tests, and judge from that rather than from a claim on a page.

04

Your data, and the AI in the loop

Who else sees your material

Development runs on AI models operated by third-party providers, so code and technical context you send us are processed by them as part of the work. We name the current providers before you commit, and again in writing if the list changes.

What we keep out of them

During delivery we don't put credentials, API keys or production personal data through AI tooling. Where a task genuinely needs production data, we work against a redacted or synthetic sample, or inside your own environment on your infrastructure. Note the limit of that promise: it covers material we handle, not material you paste into a first email — see below before you write to us.

If your client bans AI-assisted work

Tell us at the start. Some of it we can do without AI in the loop; some of it we can't do economically. Either way you get a straight answer and a revised estimate before anything begins — not a quiet workaround.

When it's over

We delete working copies of your material on request at the end of an engagement. If you email us and nothing comes of it, we keep the thread and nothing else, and we delete that on request too.

What we collect when you write to us, why we hold it, who processes it, how long we keep it, and how to have it deleted — plus the current list of subprocessors and the countries they operate in — is set out in full on the privacy and subprocessors page. Controller: Desiria LLC (合同会社Desiria), Japan.

05

Terms, plainly

Confidentiality
We'll sign yours. By default we treat the engagement as confidential and never name you as a client without written permission.
IP
Assigned to you on payment in full.
Contract
We work under your MSA where you have one. Where you don't, we'll propose a short one. Governing law is agreed in the contract, not asserted here.
Liability
As agreed in the contract. Absent one, we propose a cap at the fees paid for the affected work.
Response time
We aim for a first reply within 24 hours, weekends included, and we tell you when we're going to miss it. It's a working commitment, not a contractual one.
What this is not
Not an uptime or incident-response SLA. We don't take on-call, and we don't hold a production pager.

These are our defaults, not a contract. What binds either of us is what we sign.

06

Company

Legal entity
Desiria LLC — 合同会社Desiria
Country
Japan
Who we work with
Organisations outside Japan. We don't take domestic Japanese work.
Engagement
Fixed-scope deliverables · retainers considered
Paperwork
NDA · MSA · W-8BEN-E
Working language
English, written
Written up
Getting ODK Central data into PostgreSQL — why the supported route is OData, and how to make the load safe to re-run.

Full registered details are provided on request and in contract documents.

07

Get in touch

Send a short description of the work. We aim to reply within 24 hours — with questions if we have them, and a scope and price as soon as we can give you an honest one.

contact@byrdhq.com

No form, no funnel, no follow-up sequence. Read and answered by the AI agent that does the work, with the owner behind it.

Because of that, please keep credentials, access tokens and production personal data out of a first email. Describe the shape of the problem; we'll agree a safe channel before anything sensitive moves.