About us
A small team of senior engineers who build institutional platforms and stay to run them.
Dynamosys designs, builds and operates Drupal platforms for institutions: government, education, healthcare, nonprofits, media and entertainment. We work in your own cloud account, to the accessibility standard you are held to, and we answer when something breaks. The relationships we want are the ones that last a decade.
Let's talkWho we are
Dynamosys is a small team of senior engineers with more than ten years running a public-sector Drupal platform behind us. We started the company to do that work the way we think it should be done: one team from the first audit to the tenth year of operation, no hand-off to a hosting reseller, no ticket queue between you and the person who built your system. We are remote, we work for institutions, and we are deliberately small.
What we believe
A platform is judged years after launch, not at it. Accessibility is a property of the build, not a checklist at the end. Strategy comes before code, because the decisions that make or break a platform are made before anyone writes any. And the account, the data and the documentation belong to you, so that if we ever went away, nothing would go with us.
How we work
Every engagement starts with an audit in writing: what exists, what it costs, what is at risk. Then a plan with dates and a number, a build to Section 508 and WCAG 2.2 AA, a rehearsed migration, and a launch with monitoring and a patch schedule already in place. After launch we stay, under a support agreement with a named engineer, security releases inside the advisory window, and a monthly review of what the platform costs and what it should do next.
Who we work for
Institutions that have to pass an audit and outlast their vendors: agencies, universities and school districts, hospitals and health systems, nonprofits, publishers and studios. Our first platform has been a federal one for more than ten years, and it is still on the standard it launched to. Our client list is short on purpose. We would rather run a few platforms well than sell many and hand them off.
Four things we hold to on every platform
They are how we work, not options on a quote.
Run what you build
The engineers who design a platform are the ones on call for it. That changes how it gets built.
Accessible is the default
Section 508 and WCAG 2.2 AA in the theme and the editorial rules, checked on every change, with a report you can publish.
Your account, your data
Nothing resold. The platform runs where you own it, under your procurement and privacy rules.
Write it down
Architecture, runbooks and decisions in your repository, so the next engineer, ours or yours, can run it.
A project with a start and an end, or an engineer inside your team
Every service is delivered one of these two ways. Pick the shape first; the service follows.
We scope it, build it, and stay to run it
An audit first, a fixed plan, then the build with monitoring and a patch schedule already in place at launch.
- Migrations, upgrades, new builds, audits, remediation
- In your cloud account, to WCAG 2.2 AA
- A named engineer after launch
Senior people inside your process
Your repository, your stand-ups, your tracker, your lead. For a migration window, a backlog, or an open role while you hire.
- Drupal, cloud and accessibility engineers
- Weeks to start, month to month after a minimum
- Documentation in your wiki as the work is done
From the first call to the tenth year
The same shape whatever the sector. Decisions above the line, the steps that run on every build below.
Launch is the middle, not the end. The support agreement is where most of the relationship lives.
Tell us what you need.
A new project, an engineer for your team, or a question. We read every message and get back to you as soon as we can.
Let's talk