Services

Desktop tools

Some work belongs on the desktop, next to the files and the credentials a team already has.

We build desktop tools when a browser is the wrong place for the job. The example here is an API client for Windows: a fast application for calling REST, GraphQL, gRPC, WebSocket, and server-sent events, with workspaces, environments, and secrets kept in the operating system’s own keychain.

We’ve anonymised the copy here at the client’s request. What we’re showing is the kind of tool: their environments, their sign-in flow, and starter workspaces, brought into one application they install and use without routing requests through a third-party cloud.

Around that, the tool imports collections from the formats teams already have, filters responses, and can mirror a workspace to the file system so it lives in git. Plugins cover authentication and the small utility functions people need day to day, such as timestamps and identifiers.

If you need a different utility — a checker, a converter, a console for an internal API — we start from the task, not from a catalogue of buttons. The branding is yours: the three-line CPT frame can hold your own icon, so the tool still belongs to your family of products.