Project Cloud d.o.o., Sveta Nedelja, Croatia
Project Cloud is a small IT company a few kilometres west of Zagreb. We set up and look after the infrastructure, deployment pipelines and monitoring behind web applications, and we build the applications themselves when a client needs that too. Our engineers have been doing this kind of work for about fifteen years, much of it on public-sector systems in Croatia and for companies in Germany, Austria and Switzerland.
Most clients come to us with an application that already exists and an infrastructure that has grown around it over the years. We take over the parts that are not the application itself: where it runs, how it gets deployed and how you find out when something is wrong.
Build, test and deployment pipelines in GitHub Actions, GitLab CI or Jenkins, including container image builds and the release process around them. Where a pipeline already exists we usually start by making it reproducible before changing anything else.
Tools: GitHub Actions, GitLab CI, Jenkins, Docker, container registries
Provisioning and configuration as code with Terraform, on Oracle Cloud, AWS, Hetzner or servers you own. Networking, TLS certificates, backups and cost control are part of the job, and so is writing it down so that someone else can take over later.
Tools: Terraform, Kubernetes, OpenShift, Oracle Cloud, AWS, Hetzner, Linux
Installation and day-to-day operation of the services applications depend on: Keycloak for identity and access management, PostgreSQL, Oracle, Redis and RabbitMQ, usually as clusters, behind NGINX or Caddy. We keep them patched and we test the failover rather than assume it.
Tools: Keycloak, PostgreSQL, Oracle, Redis, RabbitMQ, NGINX, Caddy
Prometheus, Grafana, Loki and Elasticsearch, set up so that an alert reaches the right person with enough context to act on it. We also write the runbooks and rehearse the recovery steps before they are needed.
Tools: Prometheus, Grafana, Loki, Elasticsearch, on-call runbooks, disaster recovery
Web applications and company sites built with Astro, React, Angular and Spring Boot, plus the integrations and internal tools around them. End-to-end test automation comes with it where it pays off.
Tools: Astro, React, Angular, Spring Boot, TypeScript, Java, end-to-end tests
A review of an existing system, its security posture or a team's delivery process, with a written report and a prioritised list of changes. We also take on interim DevOps leadership and mentoring for teams that are building up the skills in-house.
Tools: system architecture, security review, DevOps leadership, mentoring
Engagements are usually one of two things: a fixed-scope piece of work, such as a review or a migration, or a part-time DevOps role in your team over several months. Both start with a call.Get in touch
Systems our engineers designed, built or operated, several of them before Project Cloud was founded. Most are Croatian public-sector systems with a fixed go-live date.
Croatian Bureau of Statistics
DevOps engineer, system architect
The first Croatian census carried out online. We designed and implemented the infrastructure, deployment, monitoring and disaster-recovery setup: Keycloak and PostgreSQL clusters, Prometheus, Grafana and Elasticsearch. The system stayed up for the whole enumeration period.
Stack: Docker, Jenkins, Keycloak, PostgreSQL, Prometheus, Grafana, Elasticsearch, NGINX
Ministry of Physical Planning, Construction and State Property
DevOps engineer, system architect
A web application that follows a construction project from the building permit to the technical inspection, running on the national cloud infrastructure. We designed and set up every infrastructure component: the Keycloak, Elasticsearch and PostgreSQL clusters, the web and application tiers, Jenkins and Grafana.
Stack: React, Spring Boot, Keycloak, Elasticsearch, PostgreSQL, Jenkins, Grafana
Croatian Motorways
DevOps engineer
Web, mobile and back-office applications for recording and billing tolls, on a mix of Linux and Windows servers. We built the RabbitMQ, Redis and Keycloak clusters, an application performance monitoring setup and the CI/CD process, and then supported the system in production.
Stack: .NET, React Native, RabbitMQ, Redis, Keycloak, Grafana, Elasticsearch
Ministry of the Interior
DevOps engineer
A single-page application for managing a fleet of drones and their equipment. We installed and configured the Oracle database, Keycloak and the CI/CD infrastructure, and supported the development team until delivery.
Stack: Angular, Spring Boot, Oracle, Keycloak, Jenkins
Consors Bank
DevOps engineer, developer in test
The bank's customer website rebuilt with Angular and Spring Boot. We designed and implemented the end-to-end testing framework and the Jenkins pipelines that every release has to pass.
Stack: Java, Spring Boot, Angular, Jenkins, Cucumber, TestCafe, SonarQube
TDE Thonhauser Data Engineering
DevOps engineer and team lead
Leading the DevOps team of an Austrian data-engineering company: we redesigned the CI/CD infrastructure, built the end-to-end testing infrastructure and look after the deployment process. Remote, with visits to Austria when there is a reason for one.
Stack: CI/CD, Kubernetes, end-to-end testing, team leadership
Project Cloud d.o.o. was founded in 2022 and is registered in Sveta Nedelja, a few kilometres west of Zagreb. We are a small group of DevOps and infrastructure engineers, and the people you talk to are the people who do the work. Before the company existed we worked on the same kind of systems as employees and contractors, in Croatia and for companies in Germany, Austria and Switzerland, and most of that work was remote, as it still is.
We prefer tools that have been around for a while and are well documented, and we write down what we decide and why. The aim of every engagement is that your team can run what we built without us. If you want us to stay on afterwards we can, but it should be a choice and not a dependency.
Step 1
Half an hour about what you run, what hurts and what has to stay as it is. No preparation needed on your side.
Step 2
The smallest change that fixes the problem, what it costs, what could go wrong and what is out of scope.
Step 3
Infrastructure as code, pipelines and documentation go into your repositories and are reviewed with your team as we go.
Step 4
Runbooks, monitoring and a walkthrough, so your team runs it without us. We stay reachable if you want us to.
Tell us what you are building, or what keeps breaking. We answer within one business day, and the first call costs nothing.