Your site and giving page
a campaign page you own outright, with a donate button that goes straight to your payment processor.
- monarda ↗Kitcampaign page
Modern operations, sized for organizations that run on volunteers and donations.
Most mission-driven teams rent their systems: donated software seats and free vendor tiers they don't own and can't leave. We help you move to infrastructure you own outright.
No invoice for nonprofits and volunteer-run orgs. Call when you need to, if you need to.
Four things we deliver into estates you own — each one already running in the open, because we practice what we publish. Every offering links to a live receipt: a public repo you can read, fork, and run today. Nothing here is a slide about something unbuilt.
You'll own every piece. We'll show your people how to run it. Firing us is a runbook — a fork, not a migration off a service we run.
An anti-lock-in practice is only believable if walking away is trivial. So the boundary isn't a promise — it's the standing delivery model, true by construction.
Six things every shop needs, and three for when you need them. Under each one are the parts that keep it, and every part is free to take. The codename is the part's name (they're New England native plants); the plain words say what it does.
The chip is the part's tier, which is how much work it takes to stand up in your own accounts. A Kit you clone and stand up from the repo alone. A Platform takes about a day's work with your own accounts. A Pattern you read and lift pieces from. Tiers come from the tier registry ↗, and if it disagrees with this page, it wins.
a campaign page you own outright, with a donate button that goes straight to your payment processor.
minutes, policies, and filings in one vault, the posting rules beside them, and a public board that shows what went up on time. When the board, the auditor, the funder, or the insurer asks, you send a link.
every laptop set up the same way, every login with a named owner, and leaving is a pull request, a proposed change someone else reviews before it lands.
know when something breaks before the executive director does, and a file that says who gets the call.
requests land in a list, answers come from runbooks you wrote once, and the front desk answers at 9 pm.
every export you'd need to leave a vendor, on a schedule, into a repo you own, with a restore you've drilled.
sensors, and a lobby screen that says whether you're open
a real AWS environment in your account, as code
agents that open pull requests and never merge
The map leans on these. They cost you nothing, and none of them is ours.
Not everything is a template. Custom work — audits, migrations, incident response, hardening — sized to your constraints and delivered into your estate under the same pledge. Free for nonprofits and volunteer-run organizations; everyone else, ask. Never a subscription to something we run.
Find the NAT gateway eating the budget; the IAM role nobody owns; the bucket with forgotten logs. One-page report, no theatre.
Bare metal to cloud-native and every platform shift in between. Rigor intact, planned so the people you serve don't notice.
Runbooks, alarms, and on-call rotations humans can live with. Service targets that reflect reality, not aspiration. Pager hygiene included.
Deploy pipelines with no stored passwords, every change reviewed before it applies, and signed builds — so a compromised pipeline can only reach what it was allowed to.
The full runbook is longer, drier, and in the repo. These are the six we'd bring into a room on day one.
The person who designs the system is the person who carries the pager for it. Otherwise the design is a suggestion, not a commitment.
Least-privilege isn't a checkbox — it's the default. If a compromised pipeline can reach production, the problem is the pipeline, not the compromise.
An incident handled by a sleepy engineer following the runbook is better than a hero who remembers. Write the doc. Update it when it lies.
You cannot operate what you cannot see. Logs, metrics, traces, and a single dashboard a human actually opens. No 'we'll add it later.'
Infrastructure changes are code review. OIDC, no long-lived credentials, signed artifacts. The pipeline is the contract.
A NAT gateway you forgot about is a security problem. A forgotten log bucket is a compliance problem. Run the audit monthly, not yearly.
I've kept production running around the clock since 1997: first in server rooms where every change had physical consequences, now in cloud systems defined entirely in code. These days I help organizations that run on donations run that same kind of reliable setup on infrastructure they own, and I do it in the open.
Moved to cloud-native work: infrastructure written as code, every change reviewed where the whole team can see it. The tools changed; the habits didn't. Rehearse the failure, write down the fix, make the next change boring. Lentago is where I practice those habits in the open, on an estate anyone can copy.
A much larger company bought us and put real money behind the platform. I ran disaster-recovery drills, cut recovery times, and made every component within reach redundant. Led the capacity buildout team, with a lot of vendor evaluation along the way. The job grew to cover internet routing, large email domains, DNS, CDNs, and cloud integrations.
Joined a small startup of fewer than 50 people in 2007 as its third infrastructure operator. Each instance of the platform was hardware we designed and racked ourselves: load balancers, storage, layers of network switching, one cabinet at first and later several. I made the buildouts repeatable and added redundancy wherever it would fit. Every hardware generation changed something, so I used configuration management and orchestration to keep those differences away from the support team.
Started as the overnight operator: data-center keys, orders to change the backup tapes, and escalations from support. I learned AIX and VMS from the career sysadmins I'd just woken for the third time that night, and never called anyone about the same thing twice. I earned the day shift by doing a full sysadmin's job on nights, trained my own replacement, and kept leading the night shift from days. By 2005 I was a principal operator who'd brought two new data centers from construction to production.
No invoice if you're a nonprofit, a volunteer-run org, or the one person keeping the lights on somewhere. If you know what you need, send the repo. If you don't, send the symptoms. We usually reply within a business day.