1993
Building networked systems since the web’s first years
30+
Years of continuous operation, same owner
175
Domains registered and managed since 1993
250MB
Per-sample field data moved securely from the Arctic, on a kilobit link
Three practices, one workshop
They share the same engineering discipline. They differ in who pays and why.
Research & Scientific Data Systems
Schema design, data capture and transport, instrument and field integration, controlled access. The browser is one client among several — the durable asset is the database and the pipeline that fills it.
Engineering engagements. Won through direct relationships, not advertising.
How this worksInfrastructure Custodianship
Servers, domains, certificates, mail, backups and member data for societies and associations whose systems must outlive every volunteer board that governs them. We hold the operational memory so your officers can rotate.
Annual retainer. Predictable, renewable, quiet.
How this worksInstitutional Memory & Archives
Turning an institution’s unstructured record — dead sites, orphaned mailing lists, paper, disks — into a structured, searchable corpus it owns outright. Machine-assisted processing at a scale that was not affordable five years ago.
Grant-funded. We help the institution apply, then deliver against the grant.
How this worksSelected work
In most of these the public website was the smallest part of the contract.
Calvert Internal Medicine
One of the larger physician practices in Calvert County, Maryland. We built its encrypted communications and the mail infrastructure carrying them, with certificate management alongside — at a point when secure messaging was rare in a practice of that size and the compliance expectations around patient information were tightening sharply.
Why a medical practice is different
A doctor’s office cannot treat its systems as a marketing expense. Mail has to be provably secure, certificates cannot quietly lapse, records have retention obligations, and the practice carries the liability when any of that fails. It is exactly the work this firm is built for: few moving parts, an engineer who is still reachable years later, and no vendor sitting in the middle of patient data.
Arctic Mars Analogue Svalbard Expedition
Carnegie Institution · NASA-funded
Engaged directly, without a bid, on the strength of prior delivery. Designed the database entities, the secure transport for data sets up to 250MB, the sample log carrying GPS coordinates and analysis results, and the feasibility work on streaming and remote site telemetry — for a team working off a kilobit satellite link.
Astrobiology research database
Carnegie Institution of Washington
A normalised relational schema — documents, fellowships, people, publications, local and remote resources — running on the institution’s own infrastructure. The web interface was the reporting layer on top of it.
Patent & Trademark Office Society
PTOS and its journal, JPTOS
Journal publishing workflow, membership records and an intellectual-property job board, plus the hosting and domains beneath them — carried intact across three decades of rotating volunteer boards.
Science & religion programme support
American Association for the Advancement of Science
Server build-out plus the databases behind the AAAS Dialogue on Science, Ethics and Religion: affiliate networks, seminar registration and breakdowns, speaker and consultant records, and the mailing infrastructure that drove them.
Touring production websites
Columbia Artists Management
Production sites with streaming media, fan registration and bulletin boards, built and hosted when delivering audio and video over the web was still unproven.
A diaspora’s digital record
Hungarian-American cultural institutions
A federated network of museum, association and archive systems. Thirty-plus years of a community bulletin board reconstructed from dead static pages and mailing-list exports into a single searchable, categorised corpus.
And the work that leaves no trace in a domain list
The largest engagements never ran on our infrastructure at all. For the American Association for the Advancement of Science we specified and built a server that lived at the client, running conference scheduling, registration and payment, and the affiliate and speaker databases behind a national programme. For the Carnegie Institution we built research sites and databases hosted on the institution's own machines — including personal research sites for its senior scientists — alongside the Arctic expedition software and work for the NASA Astrobiology Institute. For a physicians' practice we built encrypted communications and the mail infrastructure to carry them, at a time when almost no small practice had either. None of that appears in a count of domains, because the client held the domain. It is, however, most of what we actually did.
What we actually sell
Agencies finish projects and move on. Platforms rent you a system you never own. The institutions we serve can afford neither: a society hands its records to a new volunteer board every two years, a research programme needs its data readable after the grant closes, and an archive is worthless if it exists only while someone remembers to pay a subscription.
We sell owned infrastructure and the continuity to run it — the engineer who designed the schema is still reachable a decade later, still holds the registrations, and still knows why it was built that way.
About the firmYou own it outright
Standard SQL, standard files, your servers or ours by choice. Everything we build can be handed to someone else — including your data, in bulk, on request.
Few moving parts
No page builders, no plugin sprawl, no vendor in the middle. Simplicity is what makes a system survivable across decades.
Migration as a habit
We have moved sites off FrontPage, off dead CMSes, off hosts that vanished. Nothing gets stranded.
Accountable delivery
Defined scope, dated milestones, a written final report. Especially where grant money is involved.
The floor: servers, domains, mail, certificates, backups
We operate the infrastructure under everything above — because a system nobody is administering is a system quietly dying. This is the floor of the practice, not the reason to hire us. We do not compete on price with commodity hosts, and we do not take hosting-only accounts where we have no engineering relationship.
Tell us what has to still be working in ten years.
Research programme, member society, or a collection nobody has funded yet — start with the problem, not the technology.
Get in touch