Skip to content

Architecture review

We find what's slowing your software down.

Performance issues, unstable deployments, growing technical debt or a decision you want to validate: we analyse architecture, infrastructure and development process and tell you honestly what's worth doing.

Get in touch

Typical triggers

When a review makes sense.

  • Performance issues

    The application is getting slower, databases are running hot and nobody knows exactly why.

  • Technical debt

    Every change takes longer than the last. You want to know where to start first.

  • A big decision

    Cloud migration, a new platform, microservices? You want an independent assessment before you invest.

  • Taking over a system

    You're taking over a piece of software, internally or from a vendor, and want to know what you're getting into.

Analyse & recommend

An independent view from the outside.

We analyse your infrastructure, your software development process and your architecture, as an architecture review or a full software audit. The result: clear recommendations, a strategy or a solid basis for decision-making. And when things are on fire, we get stuck in with troubleshooting right away, from platform engineering and infrastructure automation to debugging in production.

What we look at

  • Architecture
  • Infrastructure
  • Development process
  • Code

Process

How a review works.

  1. 1

    Email with an overview

    Send us a short summary of your situation. Feel free to attach an NDA straight away.

  2. 2

    Initial call

    We get back to you with a few questions and talk to you and the relevant team members, including the uncomfortable questions.

  3. 3

    Fixed-price proposal

    We discuss everything internally and send you a fixed-price proposal. Everything is included.

  4. 4

    Results

    You get documents and reusable diagrams in your wiki or as a PDF. For 30 days afterwards, we're still available for your questions.

What you get at the end

  • Clear recommendations, a strategy or a well-founded basis for decisions
  • Documents and reusable diagrams
  • Right in your wiki or as Word/PDF
  • Free access to our expertise for 30 days after handover
30 days Money back

Not satisfied? Money back.

Up to 30 days after payment and before the final results are handed over, you can request a refund. A short email is all it takes. Everything you've received up to that point is yours to keep.

Get in touch

Case studies

Projects in this area

All case studies →
Insurance

An IT strategy built for growth and regulators alike.

Analysis of infrastructure, architecture and development process at a mid-sized insurance company, with a catalogue of measures, a hybrid target architecture and a clear view of VAIT, DORA and NIS2.

  • IT strategy
  • Kubernetes
  • Hybrid cloud
  • VAIT
  • DORA
  • NIS2
Automotive

A modern platform for .NET applications on Amazon EKS.

A modernised application environment on Kubernetes with blue-green deployments, a CI/CD pipeline and clear compliance rules, plus consulting for development and product management.

  • AWS
  • Amazon EKS
  • .NET
  • Blue-green deployment
  • Atlassian Bamboo
  • Compliance
Shipping

Vessel data in real time with Apache Kafka instead of manual services.

For a vessel data analytics provider, we moved the existing architecture of Elasticsearch and manual services to a scalable streaming architecture with Apache Kafka.

  • Apache Kafka
  • Amazon MSK
  • Kafka Streams
  • Spring Boot
  • Java
  • Schema Registry
  • Kafka Connect
  • MirrorMaker
  • GitLab CI/CD
  • Kubernetes
  • DigitalOcean

Knowledge

More on this topic

All articles →
System design 8 min read

Why file attachments don't belong in your database

Just put the profile photo or PDF into the database? What that means for operations, performance and backups, and when a filesystem or object storage is the better choice.

Christopher ·
Kubernetes 6 min read

Kubernetes for software products: worth it or not?

In many cases, Kubernetes mainly increases complexity. We show when the platform pays off for internal applications, portals and SaaS, and which alternatives exist.

Christopher ·

FAQ

Frequently asked questions

How long does an architecture review take?
Depending on the situation, anywhere from a few weeks to a few months.
How much does a review cost?
You get a fixed-price proposal. The price depends on the scope of the deliverables and includes everything. Payment is made up front.
In what form will I receive the results?
As documents and reusable diagrams, directly in your wiki or as Word/PDF. For 30 days after handover, you continue to have free access to our expertise.
What should we do about technical debt?
Don't tackle everything at once. In the review, we show you which technical debt is really slowing you down, what pays off first and what can wait.
Do you also find the cause of performance problems?
Yes. We look at the application, database, infrastructure and network at the same time, because the cause rarely sits where the symptom shows up.
Do you also do code reviews?
Yes, as part of a review we also look at the code, with a focus on architecture, security and maintainability.

Let's talk about your project.

Drop us a line about what's holding you back. You'll get an honest answer from a real person. No chatbot, no sales call.

Get in touch

You'll hear back from us within one working day. The first conversation is free and non-binding.