Request a quoteGet a quote

Custom software development · Prague

Great software often goes unnoticed. It just works.

Katka stands with her arms spread in front of the wooden doors of a house, eyes closed, face turned to the morning sun. A shot from the Solutia video.
Watch the full video (Czech)

We build custom software for businesses: web and mobile apps, data and AI, and systems integration. From analysis through development in sprints to SLA-backed support. And the code is yours.

Request a quoteWhat we build for businesses

Companies and institutions we have built software for

What we build

What we build for businesses

We choose technology to fit the brief and only pick what we can still stand behind after five years in production.

Enterprise web applications

An operations director sits at her desk next to a stack of binders covered in sticky notes, smiling at a large monitor with an order overview and charts. Behind the glass wall is a warehouse with shelving and a forklift.

Today: Orders, approvals and records live in spreadsheets, emails and the heads of a few people. To find out where something got stuck, you pick up the phone.

One place for the whole process. Everyone sees what is on their plate, management sees the status without chasing anyone, and nothing gets retyped between spreadsheets.

  • Internal portals, approval workflows, record keeping
  • Customer self-service portals
  • Roles and permissions, audit trail
  • Java
  • Spring Boot
  • React
  • Next.js
  • PostgreSQL
Architecture and process flow

  1. Trigger

  2. Orders, approvals and overviews on one screen instead of spreadsheets and emails.

  3. People see and approve only what belongs to them. Every step is written to the audit trail.

  4. The rules of the process live in code, not in people’s heads. A step that is waiting never falls through the cracks.

  5. All data in one place, so reports and overviews add up.

  6. A completed order flows all the way into accounting without anyone retyping it.

Mobile apps and PWAs

A service technician stands in a basement next to an open electrical switchboard, smiling and holding up a rugged tablet showing a ticked-off report, photos and a customer signature. A toolbox and crumpled paper forms lie on the floor.

Today: Field technicians fill in paper reports and someone in the office types them into the system later. In basements and on building sites there is often no signal either.

The job is closed on site, even without a signal, with photos and the customer’s signature. The office has the data straight away and nobody retypes it.

  • Field apps that work without a signal
  • Secure on-device data storage
  • A PWA as a cheaper alternative to two native apps
  • Swift
  • Kotlin
  • Service Workers
  • Node.js
Architecture and process flow

  1. Trigger

  2. The report, photos and customer signature are saved on the device even without a signal.

  3. Data on the device is protected and sign-in is secured with multi-factor authentication.

  4. As soon as there is a signal, the app sends the data on its own. Nothing gets lost.

  5. The data goes straight into your job management system, and the office sees it right away.

  6. The office gets a notification that the job is done, and the technician can head to the next one.

Data and AI

A planner in a logistics control room smiles and points at a wall of screens with a route map, charts and truck status. Outside the window, trucks stand at the warehouse loading docks in the setting sun.

Today: Data on orders, stock and transport sits in several systems. Planning runs on guesswork and management reports are put together by hand.

Data from all your systems in one place, and decisions based on it rather than guesswork. The dashboard shows what is happening now, and the model hints at what is coming.

  • Data warehouses and management reporting
  • Demand forecasting, anomaly detection
  • We check data quality first, then build the models
  • Vertica
  • Python
  • FastAPI
  • Kafka
  • Recharts
Architecture and process flow

  1. Trigger

  2. Events from every source flow in continuously, not once a month in an export.

  3. First we make sure the data adds up. A model built on bad data would give bad advice.

  4. All data in one place, with queries over both history and the current state.

  5. Demand forecasting and anomaly detection as a service that other systems can call.

  6. Management and planners see the current state and the outlook on one dashboard.

Integration and modernization

An IT administrator kneels in a server room, connecting a bundle of colored cables from an old beige computer with a green monitor into a modern server rack.

Today: The ERP, CRM, online shop and legacy system don’t talk to each other. Data is moved between them by hand, and nobody dares to touch the system that keeps operations running.

Systems pass data to each other on their own through a single integration layer, and you can replace the legacy system piece by piece without downtime.

  • Connections to SAP, Helios, Oracle and systems with no API
  • Gradual legacy migration instead of a risky big bang
  • An integration layer that doesn’t burden production
  • SOA
  • REST API
  • Microservices
  • Kafka
  • Kubernetes
Architecture and process flow

  1. Trigger

  2. We connect even a system with no interface. It keeps running until a new module takes over its work.

  3. Systems exchange data through one layer instead of everything being wired to everything. Production is not burdened.

  4. New parts are built alongside the legacy system and take over its functions one by one.

  5. New modules are deployed and scaled independently of each other and of the legacy system.

  6. The legacy system is switched off step by step while operations keep running.

Discuss a similar project

How we work · Six S

Behind “it just works” are six phases we watch in every project

PRINCE2®
control stages, budget and regular risk reporting
Agile
one- to two-week sprints, each ending with working software

S1SolutionsPhase 1: Analysis and design

Built around your processes, not the other way around.

We find out how your company really works: who does what, where people wait, and what still gets retyped by hand. That becomes the specification and an architecture connected to the systems you already have. It is all set down in a contract that guarantees milestones, quality and your ownership of the code.

What we solve

  1. Initial meeting
  2. Analysis and specification
  3. Contract signing

What you gain

  • Meeting notes and an indicative scope
  • Functional specification
  • Architecture design
  • Contract, schedule and budget

Architecture · 4 layers

Pick a layer

  1. UI web · mobileScreens built around roles: everyone sees just what they need for their job, on desktop and mobile.
  2. API REST · integrationsA clearly documented interface and connections to the systems you already have: ERP, CRM and accounting.
  3. Services business logicYour rules in code: approvals, calculations and notifications. Each service can be changed on its own.
  4. Data databases · reportsDatabase design, data permissions, backups and reports that answer your questions.

What we design in this layer · UI

Screens built around roles: everyone sees just what they need for their job, on desktop and mobile.

S2SimplicityPhase 2: Interface and prototype

Complex inside. Simple outside.

Before anyone writes code, we design how the app will be used. You and your users try out a clickable prototype, so mistakes get fixed before they turn into expensive rework. The validated design becomes a backlog with priorities you approve.

What we solve

  1. Interface design
  2. Clickable prototype
  3. Testing with users

What you gain

  • User interface design
  • A clickable prototype tested with users
  • A backlog with priorities you approve

S3SpeedPhase 3: Development in sprints

Fast apps. Fast delivery.

We work in one- to two-week sprints: you approve the priorities at the start, and at the end we show you working software, not a slide deck. You always know what stage the project is at. Performance is part of the design, and code review is standard, not an extra.

What we solve

  1. Team setup
  2. Development and code review
  3. Demo of working software

What you gain

  • A working increment every one to two weeks
  • An approved version and a list of changes after every demo
  • Budget and risk reports

S4SecurityPhase 4: Testing and security

Security by design, not as a patch.

Security is built into the architecture from the start; this is where we verify it: automated and by hand, including the threats on the OWASP Top 10 list, and with ethical hackers for sensitive systems. You sign off on the software in acceptance testing. Our information security management is ISO/IEC 27001 certified.

What we solve

  1. Testing
  2. Security testing
  3. Acceptance testing

What you gain

  • Test report
  • Fixed findings
  • Penetration test results for sensitive systems

Protection · attack simulation

  • Passwordsstored securely
  • Sign-inMFA where needed
  • Transportencrypted
  • CodeOWASP Top 10 tests
  • ManagementISO/IEC 27001
Attempts
179
Blocked
179
Breaches
0

Attempt log

  1. SQL injection58× blocked
  2. XSS41× blocked
  3. Password guessing47× blocked
  4. CSRF19× blocked
  5. Session hijacking14× blocked

S5ScalabilityPhase 5: Launch and growth

A smooth go-live. Growth without a rewrite.

We manage the rollout to production so your services keep running, and we train your users and administrators. The architecture is ready to grow from day one, so you can start small with a minimum viable product (MVP).

What we solve

  1. Production rollout
  2. User training
  3. Documentation handover

What you gain

  • The application in production
  • Trained users and administrators
  • Manuals or video guides
  • Technical documentation

S6SupportPhase 6: Support and further development

Launch day is just the start.

We actively monitor performance and security, and with support up to 24/7 we respond within a guaranteed time. We manage IT services in line with ISO/IEC 20000-1 and meet regularly to plan what’s next. And if you ever want to take development in-house, we’ll hand it over to your people.

What we solve

  1. Support and maintenance
  2. Further development

What you gain

  • SLA support up to 24/7
  • Monitoring and regular reporting
  • A development roadmap for the next period

Why Solutia

Security, compliance and operations

We take regulatory requirements into account from the design stage. Where we develop, where the system runs and which platform it’s built on is something we agree with you.

  • NIS2 · GDPR

    Regulatory compliance

    We take the requirements of NIS2 and the Czech Cybersecurity Act into account from the design stage. A GDPR data processing agreement is a standard part of working with us.

  • Development

    Developed in Prague

    By default, we develop on our own internal infrastructure, on servers in Prague. At your request, we can also work elsewhere, for example in a sovereign cloud. It’s a matter of agreement.

  • Operations

    On-premise or cloud

    We deploy the system on-premise on your hardware or in the cloud. We have experience with AWS, Oracle Cloud (OCI), Azure and Google Cloud.

  • Platform

    Open source, Oracle for critical systems

    We mostly build on open source, with no vendor lock-in. For critical applications, we can build on Oracle: we’re an Oracle partner and have worked with it for over 20 years. We’re also a Microsoft partner.

A selection of technologies we work with

  • Java
  • Spring Boot
  • Maven
  • Kotlin
  • Swift
  • TypeScript
  • React
  • Node.js
  • Python
  • MySQL
  • PostgreSQL
  • Oracle Database
  • Vertica
  • Red Hat
  • Kubernetes
  • AWS
  • Oracle Cloud (OCI)
  • Microsoft Azure
  • Google Cloud

  • You own the code

    Once the work is finished and paid for, the source code and all rights to it (including copyright) transfer to you. No vendor lock-in: where it makes sense, we build on open standards.

  • A budget without surprises

    No hidden fees for integration or training. We work out the total cost of ownership (TCO) up front, not on the invoice.

  • For years, not one project

    Documentation, SLA-backed support and further development as your business grows. We’re your partner for future growth.

  • ISO9001

    quality

  • ISO/IEC27001

    information security

  • ISO/IEC20000-1

    IT service management

  • ISO14001

    environment

  • since2004building software
  • 30+specialists on the team
  • 100+clients
  • AAAtop credit rating · Dun & Bradstreet
  • up to24/7SLA support

Team

Who you’ll work with

Interested in development? Email us at sales@solutia.cz or use our contact form.

Hover over a person to see their contact detailsTap a person to see their contact details

Martin Stufi

COO & CFO

Email
martin.stufi@solutia.cz
Phone
+420 252 545 447

Martin Milý

CEO

Email
martin.mily@solutia.cz
Phone
+420 267 316 318

Kateřina Beková

Back Office Assistant

Email
katerina.bekova@solutia.cz
Phone
+420 267 316 318

Miljan Pajić

Lead Software Development

Email
miljan.pajic@solutia.cz
Phone
+420 601 289 723

Vojtěch Kubka

Key Account Manager

Email
vojtech.kubka@solutia.cz
Phone
+420 721 414 404

Snežana Milovanovićová

Project Manager

Email
snezana.milovanovicova@solutia.cz
Phone
+420 773 486 900

Betty

Team dog · moral support

Doesn’t answer emails – reach her through Snežana.

FAQ

Frequently asked questions

These are the questions businesses ask us most. If yours isn’t here, just ask us directly.

Ask us
  • Why don’t you list client references on your website?

    Most of our projects are covered by non-disclosure agreements, and we treat yours with the same confidentiality. At the first meeting, we’ll describe similar projects to the extent our contracts allow.

  • Who will own the source code and the intellectual property?

    You will. Once the work is finished and paid for, the source code and all rights to it (including copyright) transfer to you. We don’t use proprietary locks that would keep you with us against your will. We want you to work with us because you want to, not because you have to.

  • Will you sign a non-disclosure agreement before our first meeting?

    Yes, we’ll sign a non-disclosure agreement (NDA) before the first meeting.

  • Can you handle a larger project?

    Yes. We work with other partners and software development companies, and on a larger project we can outsource some parts of it.

  • Can you connect the new software to our existing systems, such as SAP or legacy databases?

    Yes, systems integration is one of our core strengths. We connect modern applications to ERP systems and to older technologies that have no standard API. We design the integration layer so data flows securely and puts as little load as possible on your day-to-day operations.

  • What will you need from us during the project?

    Mainly a contact person or product owner on your side, time from key users for the analysis and sprint reviews, and access to the systems and data the new software will work with.

  • How do you keep the project from going over budget?

    We combine the firm framework of PRINCE2 with the flexibility of agile development. At the start of every sprint, you know what we’ll build and in what order. When a new requirement comes up, we assess its impact on budget and schedule together, and you decide. That way, costs stay under your control.

  • Do you build exactly to our specification?

    Yes, we always deliver the agreed functionality, processes and scope. But we don’t follow the brief blindly: if, during design or development, we spot a logical flaw or a better, simpler solution, we tell you and propose an alternative. You decide whether to take it.

  • Do you use AI in development?

    Yes, we use AI tools where they help us develop faster. Experienced developers oversee their use and look after both quality and the long-term maintainability of the code. What makes the difference is our people’s experience, especially in architecture, application logic and UX/UI – making the software easy to use.

  • Can our in-house team take over development later?

    Yes, we plan for that from the start. We write maintainable code that other developers can easily follow, structure it according to modern standards and keep thorough technical documentation. When the time comes, we hand the project over to your people and help them carry on smoothly.

Contact

Tell us about your project

Tell us what you need to build or improve. We usually reply within 24 hours on business days and agree on next steps with you.

We’ll reply to this address.

Prefer a call? We’ll give you a ring.

A few sentences are enough: what the software should do, who it’s for and, if relevant, your timeline. Up to 5,000 characters.

This form is for business inquiries about custom software development.

Solutia video