Starhold Software · automation and platform engineering

Automation and platform engineering for teams that outgrew scripts.

You wrote a script. Then a folder of them. Now something that matters depends on them — I build the version that holds, and I keep it running.

Things you can check before you read another word

What I sell

Four ways to hire me

Scoped and quoted per job. No retainer, no minimum, no discovery-phase invoice.

Published uptime

Uptime you can open

Every service I run reports to a public status page, including when it is down. You never have to ask me whether something is up.

Open the status page →

# public hostnames

starhold.devstorefront

starhold.fyidocs

starhold.appplatform

open https://status.starhold.fyi

The shape of the page. The live state is only ever on the page itself.

Verified payments

Money is verified

Payments go through Stripe Checkout. The webhook checks Stripe's signature on the raw request before it touches an order, and a request that fails the check is rejected and does nothing.

Read the source →

stripe-signatureread from header

constructEventraw body, signing secret

signature validverified

checkout.session.completedorder posted to Discord

signature invalidrejected, nothing runs

tests in this repository180 unit, 87 browser

The order of operations in the handler. Field names only, no payloads.

Self-hosted

Hosts I administer

The hosts are mine to administer, joined by a private mesh, and the services run rootless: unprivileged containers rather than a root daemon.

See the platform →

podman ps

NAMESRUNS AS

webunprivileged user

gatusunprivileged user

The shape of the output. Container names are the ones I run.

How it works

From first message to running in production

  1. A short call

    You tell me what you keep doing by hand. I ask questions until I can say what it takes and what could go wrong.

  2. A written quote

    I write down the scope and the price before I start, so you know what you are agreeing to.

  3. I build it and keep it running

    I ship it, host it where it belongs, and stay on the hook for it. If it breaks overnight, it is my problem.

The fleet

Selected work

Four things I built and still run. Each one is here because of what it proves, not because it is for sale.

How I work

Operating principles

The three above get their own space. These are the rest, short enough to remember and specific enough to hold me to.

  • Tests ship with the work. This storefront alone carries 180 unit tests and 87 browser tests, and the counts on this page are generated from the repository rather than typed in. Read them →
  • Your visit is not the product. No analytics, no ad trackers, no cookie banner. Nothing on this site phones home — the cart lives in your browser until you check out, and payment goes to Stripe. Read the policy →
  • Design notes come before code. The architecture for the platform in development is written up and published where you can read it.

Who you are hiring

Quadstronaut

I run Starhold Software. It is one person, and that person is me.

Questions

Before you ask

Who does the work?

One person. I am Quadstronaut: I scope, build and run every project myself, so the person you talk to is the person writing the code.

How I work →

How does a project start, and how is it priced?

A short call, then a written quote. Anything bespoke is governed by that quote.

What about refunds?

Subscriptions can be cancelled at any time and run to the end of the period already paid; fees already paid are not refunded or pro-rated. Refund terms for custom work are set out in each written quote. A charge that looks wrong: email me first and I respond within five business days, and you keep your card network chargeback rights either way.

Refund policy →

Where does it run?

On a dedicated server and a VPS that I administer myself, joined by a private mesh. The status page is public, so you can check it yourself.

Privacy policy →

How do payments work?

Checkout is Stripe. Card details are entered on Stripe, not on this site, and the cart stays in your browser until you check out.

Does this site track me?

No analytics, no ad trackers and no cookie banner. The privacy policy spells out what is kept.

Read the policy →

Next step

Tell me what you keep doing by hand.

Send me the process, the two systems that refuse to talk to each other, or the thing that keeps breaking overnight. I will tell you what it takes to fix it and what it costs.

  • No cookie banner — there is nothing to consent to.
  • A short call, then a written quote
  • No retainer, no minimum

Currently taking work for Q1 2027.