Product Engineering

Web Apps

Web applications are still the backbone of how the internet gets used. Even a mobile-first product leans on one for its content and for keeping state in step across devices and users. This is where that back end gets built.

Talk To Us

Back-end platforms

Java

Java is where the long-lived back ends go. Write once, run anywhere is the reason it survived, and it is still the safest answer when a service has to keep running unattended and scale sideways. Fidenz has been shipping Java back ends for years, for clients who needed the thing to still be running long after the project closed.

Spring BootMicroservicesJVM tuning

The Microsoft stack

.NET

Microsoft's stack has been the default for small and medium enterprises for decades, and the documentation and support around it are a real advantage rather than a marketing one. We build on it end to end, deploying through Azure, IIS and MS SQL Server. Its ability to interoperate across languages and systems is usually why a client picks it.

AzureIISMS SQL Server

Our primary web framework

Ruby on Rails

Rails is Fidenz's primary framework for web application development, and the one our engineers reach for first. We use a tight set of gems rather than a sprawling one, integrate against open standards, and have contributed back to open source along the way. Deployment targets have varied a lot over the years and the applications have held up across all of them.

Open standardsThird-party integrationMixed hosting

Selected Work

Where It Has
Actually Run

Client work tagged to this capability, pulled from the collection rather than listed by hand.

All client work

Ready When You Are

Have A Back End
That Needs Building?

Tell us what it has to do and what it has to survive. We will tell you what we would use and why.