These organizations had live users, fixed deadlines, aging systems, or recurring failures. See what was at risk, what Lombiq changed, and what happened next.
Different sectors, same constraint: the platform had to keep serving the organization while the work moved forward. For regulated and public-sector platforms, accessibility, security, and compliance requirements are part of the delivery constraints.
Problem
Global Health needed flexible forms inside MasterCare+ for healthcare scenarios that its existing form tools could not support.
Work
We integrated and extended Form.io, connecting the form builder to the product's business logic and data storage.
Result
Global Health gained a form-building feature designed for varied healthcare workflows.
Problem
After moving from Orchard 1 to Orchard Core, the city's website still needed regular upgrades, better tests, and performance work.
Work
We handled breaking changes, expanded automated checks for accessibility and security, and resolved performance bottlenecks in custom code.
Result
The website remains stable, secure, and easier for the city's team to evolve.
Problem
Enabling or disabling a feature could randomly take down a platform serving 50 venue sites. Live Nation's own team was already at capacity.
Work
We investigated the hard-to-reproduce failures, found the hosting problem behind them, and supported the team with further platform issues.
Result
The platform became much more stable, and the collaboration continued as further issues and questions came up.
Problem
Smithsonian Folkways had to preserve and manage a 75,000-track archive, but its aging platform could no longer support the search, streaming, and internal workflows the collection needed.
Work
We migrated the system to Orchard Core and built the custom collection management, indexing, search, streaming, and audit features around it.
Result
The platform now supports both the public website and the team's day-to-day collection work, with faster browsing and better internal control.
Problem
Topcon needed several Aptix features ready for a ConExpo demonstration, with a fixed release deadline already approaching.
Work
Our developers joined quickly and worked on integrations, workflows, front-end behavior, and theming with little overhead for Topcon's team.
Result
Topcon met the milestones leading up to the ConExpo presentation.
Lombiq has gone above and beyond to ensure that the work done in our engagement with them not only met our expectations but also surpassed them.
A few shorter examples from production systems, migrations, and launches.
Tell us what must keep working, what is getting in the way, and what happens if the problem continues. We will help identify a sensible next step.