Independent software studio

Web applications and internal tools, built to be maintained.

Unki Studio works with small teams on websites, stores, web applications and internal tools. We replace manual processes, connect systems and ship software that stays readable after handover.

Start a project What we build

A wooden desk beside a window, with a laptop, a notebook and a mug of coffee.

Services

What we build

Projects start in different places: a process that has outgrown spreadsheets, a site that no longer fits, or a product that needs its first serious version. We take the work from scoping through to deployment.

Web applications

Customer portals, dashboards and internal tools. Full-stack, from the data model and permissions through to the interface your team uses every day.
Websites and ecommerce

Landing pages, marketing sites and online stores. WordPress and Shopify where they fit, custom builds where they do not, set up so you can edit the content yourself.
Data, APIs and automation

Schemas that hold up, migrations that do not surprise you, and integrations that talk to the systems you already run. Scheduled jobs and scripts that report when they fail.
AI integration

Assistants, extraction and summarisation where they remove real work. We define the failure cases and add review points before anything reaches a user.

Also: interface design, design systems and mobile apps when the project calls for them.

Diagram of a typical build: a web interface connects to an API, which reads and writes to a database and calls external services for payments, email and models.

How an engagement runs

First: A short discovery and a written plan, before any code.
Then: Fixed scope or a weekly rate, agreed up front.
At the end: Repository, documentation and deployment handed over.
After: Support and maintenance, if you want it.

Approach

How a project runs

Short cycles, working software at every stage, and no reveal at the end. You see what is being built while it is still easy to change.

1–2 weeks
Scope

A short discovery to define the problem, the constraints and the smallest version worth building. You get a written plan and an estimate before any code is written.
Weekly
Build

Working software in weekly cycles. You can test each increment, change priorities and correct course while changes are still cheap.
Final week
Handover

Deployment, documentation and a walkthrough. The codebase stays in a state your next developer can pick up.

A laptop on a counter by a floor-to-ceiling window, looking out over a city in flat daylight.

Studio

A small team, deliberately.

Unki Studio is an independent software studio. We build client products, internal tools and a handful of public utilities that we use ourselves.

We stay small so the person who scopes the work is the person who builds it. That keeps decisions close to the code and shortens the distance between a question and an answer.

Direct collaboration: You talk to the people doing the work, not an account layer.
Privacy by default: No unnecessary data collection and no third-party tracking.
Code you can keep: Clear structure, documentation and no lock-in.
Languages: English and French.

Tools

Tools we maintain

Small utilities, free to use. Everything marked local runs entirely in your browser; nothing is uploaded.

Questions

Before you get in touch

The practical questions that come up before a project starts. If yours is not here, ask it directly.

What does a project cost?

We price by scope. After a short discovery you get a written estimate, either fixed price or a weekly rate, before the build starts.

How long does a project take?

Most projects run between four and twelve weeks. A small tool is quicker; a full application with several integrations takes longer. The written plan includes a schedule.

Can you work with an existing codebase?

Yes. We take over maintenance, extend an existing product, or audit a codebase before you commit to changes. We can also embed with your team for part of a project.

Who owns the code?

You do, under the terms of the contract. At handover you get the repository, the documentation and the deployment details.

Contact

Tell us what you are working on.

A short note is enough. Describe the problem, who it affects and any deadline. We reply with questions or a clear next step.

Web applications and internal tools, built to be maintained.