About Switchyard
Switchyard Software is an independent engineering practice in Pennsylvania. It builds integrations, internal tools, and modernizations for established businesses, and one engineer is accountable for a project from the first call to the last deploy.
Where the experience comes from
Five years of owning production systems end to end, in three domains where being wrong has a cost.
Automation at scale
The scheduling core of a large automation platform: the service that decides when every scheduled run fires, the audit log that records what it did, and the safeguards that cap what a bulk action can touch. Work where a missed run is a customer's missed deadline, and an extra run is worse.
Alongside it, the back end for a visual builder that lets people assemble their own automations: the data model, the API, and the authorization rules that decide who can change what.
Payments and identity
A customer-facing payments SaaS with a single engineer responsible for scoping, design, and delivery. The authentication system was migrated off a deprecated provider while staying compatible with every existing account, so nobody was locked out on the day it switched.
Multi-factor login and PCI-compliant card processing shipped on top, along with a public API that outside systems could integrate with safely.
Clinical software
Software used in hospitals, where a legacy interface was moved to the web without disrupting the clinicians who depended on it. Ownership of a team's performance process: weekly response-time analysis, investigation of anything that slowed down, and the fixes that followed.
The habit that came out of it is the one the practice still runs on, which is to measure first, change one thing, and measure again.
Built to be trusted while nobody is watching
Every system Switchyard ships is built on the same release discipline. New behavior is deployed switched off, verified against real data in production, and only then turned on, so shipping and releasing are two separate decisions. Every change lands behind an automated test suite before it is deployed.
Anything that spends money or sends email has a kill switch an operator can throw in one move. Anything that fails lands in a queue a person can read and replay, and every step writes a structured log line with a stable name, so when something drifts the system can say which number moved. A daily summary carries the handful of things that need a decision.
None of that shows up in a demo, and all of it is why the systems keep running a year later.
What the work is built with
Chosen because they ship quickly, run reliably, and stay maintainable years after launch. Running something else is fine, since Switchyard integrates with most of what a business already uses.
- TypeScript and React
- C# and .NET
- Java and Spring
- Python
- PostgreSQL and SQL Server
- Cloudflare and AWS
- QuickBooks and Stripe
- Google Workspace
- Twilio and Resend
There is also a set of free calculators and checkers on this site that any business can use without signing up for anything.
The next step is a conversation
The first call is free and takes thirty minutes. You describe the problem, and Switchyard says whether software is the right answer and what the diagnostic would cover.