In short

Rui Codex deploys, migrates and runs the software it builds: CI/CD pipelines, Docker containers, application and database migration with a rehearsed cutover, backups with tested restores, and monitoring with SLA-backed support and a 99.9% uptime SLA. It runs on your own infrastructure or on Microsoft Azure, AWS or Google Cloud, in the region you choose.

We work on site in Belgium and the Benelux and deliver projects remotely across Europe, including Germany, Austria, Switzerland and France, in English, Dutch, French, German or Turkish, with the GDPR applied to all work.

We also build and publish our own mobile apps and games. See our apps and games

Does This Sound Like Your Business?

If these sound familiar, the problem is usually how the software is run, not the software itself.

One ageing server carries everything

Your business application runs on a single machine nobody wants to touch. Updates are postponed, capacity is guessed, and one hardware fault would take everything down with it.

Releases done by hand

Every release is a list of manual steps that one person remembers. Releases happen rarely and late at night, and a failed one is rolled back from memory rather than by a script.

Backups nobody has restored

Backups run every night, but nobody has ever restored one. How long the business would be down after a failure, and how much data would be lost, are guesses.

No clear answer on where data lives

Customers and auditors ask which provider and which region hold their data, who can reach it and how long it is kept, and there is no documented answer to give them.

Cloud as Part of the Software, Not a Separate Product

Rui Codex designs, deploys and runs the software we build. The architecture, the release pipeline and the production environment are planned together with the application, so going live is a routine step rather than a separate project handed to someone else.

We deploy on your own infrastructure or with the cloud provider you choose, Microsoft Azure, AWS or Google Cloud, in the region your data rules require. We also run production back ends for our own published apps, so the monitoring, backups and updates we set up for you are the ones we rely on ourselves.

99.9%
Uptime SLA
100%
Your code, pipelines and runbooks
12+
Years of engineering experience (founder)
200+
Projects delivered in our founder's career

Key Capabilities

Everything between finished code and an application your business can rely on.

  • CI/CD Release Pipelines

    Every change is built, tested and deployed by a pipeline on GitHub Actions or Azure DevOps, so a release is a repeatable step rather than a manual procedure, and rolling back is a script, not a memory.

  • Containers with Docker

    Applications packaged in Docker containers run the same way on a test server and in production, which takes environment surprises out of a release and keeps a later move between providers possible.

  • Application and Database Migration

    Moves from an on-premise server to the cloud, or between database versions and engines, planned with a rehearsed cutover and row-count reconciliation, so you know what moved before you switch.

  • Backup, Restore and Failover

    Backups whose restores are actually tested, plus written backup, restore and failover runbooks, so recovery time and acceptable data loss are figures agreed in advance rather than guesses.

  • Monitoring and SLA-Backed Support

    Monitoring, alerting and performance dashboards in production, with SLA-backed support tiers, guaranteed response times and a 99.9% uptime SLA for business-critical applications.

  • Data-Residency-Aware Deployment

    Your own infrastructure or a European cloud provider and region you choose, with every data flow documented, for customers and auditors who ask where their data is stored.

How We Work

From the first review of your current setup to running the application after launch.

  1. 1

    Assess

    We review the application, servers, data volumes and dependencies, and agree targets for availability, recovery time and where the data must stay.

  2. 2

    Design

    Together we choose the hosting model, your infrastructure or a cloud provider and region, and design the environments, the release pipeline and the backup plan.

  3. 3

    Automate

    We build the CI/CD pipeline, package the application in containers where it fits, and set up monitoring and alerting before anything goes live.

  4. 4

    Migrate

    We rehearse the cutover on a copy, reconcile row counts, then switch over with a tested rollback path and your team informed.

  5. 5

    Run

    Monitoring, security updates, tested restores and SLA-backed support keep the application healthy after launch, with every change shipped through the same pipeline.

Real-World Use Cases

Cloud work we take on as part of the software we build.

  • Multi-Tenant SaaS with Isolated Tenant Data

    Several businesses on one platform, each with its own separated data, on a cloud architecture that grows as tenants are added. This is how the E-Pool Aqua platform was built.

  • On-Premise Database to the Cloud

    An internal SQL Server database moved from an office server to Azure SQL or another cloud database, with a rehearsed cutover and row-count reconciliation before the switch.

  • Mobile App Back End with Cloud Backup

    An ASP.NET Core API and database behind a mobile app, with accounts and cloud backup, of the kind we run for our own published apps.

  • Automated Releases for an Existing Application

    An application that is still deployed by hand gets a build and release pipeline, so updates ship as a routine step and every release can be traced and rolled back.

  • Monitoring for a Business-Critical System

    Health checks, alerts and performance dashboards on an application your team depends on, so the monitoring notices a problem before your users report it.

  • Hosting Answers for a Procurement Review

    A documented answer to where data is stored, who can reach it and how it is backed up, for customers in healthcare, finance or the public sector who ask during procurement.

Technology We Use

The platforms and tools we deploy and run on, chosen per project with you.

Microsoft Azure AWS Google Cloud Docker GitHub Actions Azure DevOps ASP.NET Core SQL Server PostgreSQL Appwrite (self-hosted) PostHog (self-hosted)

The full stack we work with, and how deployment and monitoring fit into our development method, is set out on our technology and methodology page.

Frequently Asked Questions

Common questions about deploying, migrating and running your software.

The one that fits your situation. If your company already works with Microsoft, Azure is often the natural choice; AWS and Google Cloud are equally possible, and so is your own infrastructure. We compare the options on the services the application needs, how it will be run day to day and where the data may be stored, and you take the decision.

Yes, that is what the rehearsal is for. We migrate a copy first, compare row counts table by table, time the cutover and agree a rollback path. The live switch happens only after the rehearsal has passed, in a quiet period agreed with you.

Where you decide. We deploy on your own infrastructure or with the cloud provider and region you choose, including European regions, and document every data flow. The provider and region you pick determine where the data is stored, and that choice is written down before we deploy.

Yes. We offer maintenance with monitoring, security updates, backups with tested restores and SLA-backed support tiers with guaranteed response times; business-critical applications run under a 99.9% uptime SLA. Changes keep going through the same release pipeline.

Our cloud work covers the software we build for you, including existing applications we take over to modernise or extend. We do not operate general IT infrastructure, office systems or workloads we are not developing.

No. The source code, the pipeline definitions, the deployment documentation and the runbooks belong to you, and you receive a complete handover package. Containers and standard databases keep a later move to another provider possible.

Personal data stays with the provider and in the region agreed with you, access is limited to the people who need it, and every data flow is documented. Where the work gives us access to personal data, we sign a data processing agreement under Article 28 of the GDPR.

Yes. We can deploy into infrastructure that your IT team or your current provider runs, hand over the pipeline and runbooks, and agree in writing who is called for what when something goes wrong.

Application by application: with you we choose between moving it largely as it is to new servers (rehosting), adapting it to cloud services such as a hosted database or containers (replatforming), and reworking the parts that hold it back (refactoring), and we change no more than your goals require. Every migration is rehearsed on a copy first, with row counts compared table by table, a timed cutover and a tested rollback path before the live switch. This covers the software we build for you and existing applications we take over to modernise, not general office IT.

For the software we build or take over, it covers a release pipeline on GitHub Actions or Azure DevOps that builds, tests and deploys every change the same way, Docker containers where they fit, monitoring and alerting, backups with tested restores, and written runbooks for releases, recovery and failover. If you want us to run the application after launch, monitoring, security updates and SLA-backed support continue from there. The code, the pipeline definitions and the runbooks belong to you, so your own IT team can work with them alongside us or after a handover.

Mostly how much of the application has to change: moving it largely as it is takes far less work than reworking it. The number of applications and databases, the data volume, the downtime you can accept during the switch, your availability and recovery targets, any rule on where the data must stay and whether we run the application afterwards add to the scope. After the review of your current setup, you receive a plan before anything moves.

Delivered work

Real projects rather than scenarios - what was built, and how.

Products we build and run ourselves

Live apps and games we designed, built and still maintain, with the same engineering we bring to client work.

See all our apps and games

Where we work

Rui Codex is a Belgian company and works on-site with clients across Brussels, Antwerp, Ghent, Leuven and Liège, serves clients across the Benelux (Belgium, the Netherlands and Luxembourg), and delivers projects remotely across Europe. See all service areas.

Outside the Benelux: how we work with companies across Europe.

Ready to Run Your Software on Solid Ground?

Tell us where your application runs today and what worries you about it. We will come back with a plan for hosting, releases, backups and monitoring.

Free consultation. No commitment. You keep the code, pipelines and runbooks.