Services

Windows software
that runs for years.

Not every job belongs in a browser. Some software must reach the disk, run while nobody is logged in, and keep working when the internet does not. We build that kind of application, and we have supported our own since 2018.

Book a discovery call

Who this is for

Desktop is the right choice more often than people expect.

Work that touches the machine

Backups, file processing, device control, scanning, and printing need access a browser will not give. A desktop application talks to the disk and the hardware directly.

Sites with poor or costly internet

A mine site, a clinic, or a rural branch cannot depend on a link that drops. Desktop software keeps working offline and syncs when the connection returns.

Data that must stay on site

Some records may not leave the building, by policy or by law. A desktop application keeps the data on your own machines and your own network.

How we work

Desktop software reaches machines we cannot log in to. That shapes every stage of how we work.

Understand

We start with the machines, not the screens. Which Windows versions, what permissions, how the software gets installed, and who fixes it when it breaks. Then we agree the scope, the price, and what the first release must do.

Build

We give you signed installers early and often, so you test on your own machines instead of ours. We test on clean systems and on machines with old versions already installed. Every release is versioned, so we can always tell which build a user is running.

Support

We ship the installer, the update mechanism, and the documentation together. When a user reports a problem, logs and crash reports tell us what happened on a machine we cannot see. We keep the application working through Windows updates for as long as you need it.

What’s included

Shipping an application is more than the program file. This is what comes with it.

A native Windows application built for the versions you run
A signed installer and a silent option for IT rollout
An update mechanism so users get fixes without a visit
Local data storage with backup and restore built in
Logging and crash reports that make support possible
A user guide plus a training session for your staff
Source code in your repository, yours to keep

We ship our own desktop product

You do not have to take our word for it. IvyBackup is a Windows backup application we have built, released, and supported since 2018.

IvyBackup

IvyBackup protects files on Windows machines in more than 20 countries. It writes drive images, full, mirror, differential, and incremental backups, and encrypts them with 256-bit AES. It speaks 8 or more languages.

Backup software is unforgiving. If it fails once, at the moment a disk dies, the user has lost everything. Years of shipping it taught us how to install cleanly, update quietly, and handle the strange state of a real customer machine. Your project gets that experience.

See IvyBackup →

Shipped and supported since 2018
Users in more than 20 countries
Drive image, full, mirror, differential, and incremental backups
256-bit AES encryption
Available in 8 or more languages
Years of installer, update, and support experience

What we build with

We stay close to the platform. Native tools give the small download, low memory use, and clean install that desktop users expect.

C#/.NETC++SQLiteWindows installer toolingWindows servicesCode signingAutomated buildsCrash and log reporting

Common questions

What clients ask before they commit to a desktop project.

Do I own the code?

Yes. You own the deliverables. Source code, installer scripts, build configuration, and documentation are yours and live in your repository. We also hand over the signing and release process, so you are never locked to us to publish an update.

How do you charge?

For a clearly scoped application we give a fixed quote before work starts. For larger work we use milestones with a price for each, and you pay as each one is delivered. We agree the model during the discovery call. Code signing certificates and any third-party licences are separate and bought in your name.

How long does a project take?

A focused internal tool usually takes six to ten weeks to first release. A product for outside customers takes longer, because installers, updates, and support tooling are real work. We give a schedule after the discovery call and put a testable build in your hands early.

What happens after launch?

Desktop software needs care for as long as it runs. We fix defects found in the agreed period after release at no extra cost. After that we offer a maintenance agreement covering Windows compatibility, security updates, and new features. We have done exactly this for IvyBackup since 2018.

Have a job for the desktop?

Tell us what the machine must do. We will say whether desktop is the right place for it, what we would build, and what it takes to keep it running. The call is free and there is no obligation.