Software customization
Open source,
extended to your workflow.
Most teams end up buying a fifth SaaS product because no single one fits, then paying again to glue them together. We start from an open-source application you are allowed to change — and change it, on a server you control.
What we actually change
Not "bespoke software". Specific edits to a real application, in the places where an off-the-shelf tool stops matching how you work.
Fields, states and views
The statuses, custom fields, forms and list views your process needs, rather than the shape the upstream project happened to ship.
Integrations between tools you already run
Helpdesk into CRM, CRM into accounting, chat into alerting. This is usually the actual reason a team is paying for one more product.
Importers and exporters
Getting data in from the system you're leaving, and back out in whatever shape your accountant, your warehouse or your regulator asks for.
Single sign-on and permissions
Wiring the app into the identity provider you already have, and setting roles up so people can reach what they should and nothing else.
The report the product doesn't ship
Queries against your own database, on a schedule, in a format you can hand to someone — because the data is on your server and it's yours to read.
Branding and deployment
Your domain, your logo, your certificates, configured on your machine as part of standing the application up.
Start from something in our open-source catalog, or from an application you already run. Either works — what matters is that the source is available to change.
How it works
You can stop after step two and it will not have cost you anything.
01
Tell us what doesn't fit
Which application — ours or one you already run — and the specific thing it won't do.
02
We scope it and quote it
In writing: what we'll build, what we won't, how we'll handle upgrades afterwards, and what it costs. The scoping conversation and the quote are free.
03
We build it on your server
Deployed on your own machine, with root access, and with the code that produced it in your hands.
04
You decide about upkeep
Leave it exactly as it is, or take managed updates or an advisory retainer. Both are optional and separately priced.
What it costs
Free
The scoping conversation and the quote
No charge, no card. You find out what the change would involve and what it would cost whether or not you go ahead.
Quoted up front
The build itself
Priced per engagement after scoping. Nothing is charged until you've approved a written scope at a written price, and nothing about the work is billed as a surprise afterwards.
Optional, and published
If you want us to keep the thing running afterwards, these are the rates — the same ones in the configurator.
- Managed OS and application updates, per server
- $19/mo
- Migration specialist (one-off session) — 60 minutes with an engineer, charged once
- $99 one-off
- Ongoing advisory retainer
- $299/mo
Installing an app is not customizing it. Deploying anything from the one-click catalog onto your server carries no surcharge — that's the product. Changing the application is a service, and it's charged separately.
The server underneath is priced like anyone else's: a flat monthly VPS tier from $4.99/mo to $89.99/mo, or a dedicated machine at $199/mo. Billed monthly in advance.
What we're not claiming
- We can't customize software we don't have the source to. If the tool that doesn't fit is closed-source SaaS, the honest options are to move to something open — that's a data migration — or to leave it alone.
- Open source doesn't mean anything goes. Licenses differ, and some place real obligations on what you have to publish or how you can redistribute. We read the specific project's license before we quote, and tell you what it requires of you.
- Customizations and upstream updates pull against each other. The further a project drifts from upstream, the more work every future upgrade is. Which side of that trade you're taking — stay close to upstream and keep the changes thin, or fork it and own it — is decided in the scope, not discovered a year later.
- No turnaround SLA. We don't publish a delivery time for custom work; the timeline goes in your written quote. The only two timing commitments anywhere on this site are that servers are provisioned within 24 hours of an order, and that we reply to messages within 48 hours.
- No case studies, no logos, no client count. Olympia is new. There is no social proof on this page because there is none to show yet, and inventing some would tell you nothing true about the work.
Tell us what doesn't fit
Describe the application and the thing it won't do. You'll get a written scope and a price, for free, and you're free to walk away with both.