Skip to content
Mon–Fri · 09:00 — 12:00 New YorkReply within 1 business daycontact@ferwyn.com
FerwynContact
FerwynToggle navigation

Read our code before you hire us

Most of what we build belongs to clients and stays private. What we can publish, we publish in full — commit history, issues and rough edges included — because it is the only claim on this site you can verify without talking to us.

Why we do it

An agency site is a series of claims a reader has no way to check. Working code is the exception: you can read how it handles the case it is bad at, whether the errors say anything useful, and whether the README is honest about what the thing will not do.

We are aware this attracts engineers rather than buyers. That is fine — it is aimed at the technical person a buyer asks before signing, and at the buyer who is technical enough to look.

The project

OfflineTasks

A Windows maintenance tool that runs cleanup jobs at the one moment they always work — right after reboot, before anything can lock a file. Jobs are declared in JSON and executed by PowerShell, so the administrator who has to trust it can read it.

Ferwyn on GitHub →

Licence
MIT
Written in
PowerShell · JSON
Scope
Windows housekeeping

What it deliberately cannot do

The README opens with this list rather than with features. Each item removes something someone would find useful.

No arbitrary commands
It will not run whatever a config file tells it to. The set of actions is fixed and reviewable, which is the whole reason it can be trusted with administrator rights.
No network
Nothing is fetched, reported or sent anywhere. A maintenance tool with a network stack is a maintenance tool with an attack surface.
No persistence
No installed service, no resident process. It does its work in the window after reboot and is gone.

From reading code to hiring us

OfflineTasks is a small tool, and it is not what we sell. What it shows is the habit: state the limits first, keep the thing readable by whoever has to operate it, and leave the history visible.

The systems we are paid for are larger and private, but they are built the same way. The case studies name what constrained them.

Read the case studies →What we build →

Read something and want to ask about it?

Questions about the code are the easiest conversation to start, and they tell us more about your problem than a brief form sometimes does.

Ask us something

We reply within 1 business day. No sales calls unless you ask for one.