From the PMC teamDevelopment projects start in 2027. Plan yours now to secure an early start.

DevOps and CI/CD

From commit to production, without manual steps.

We set up build, test and release pipelines with GitHub Actions, GitLab CI or Jenkins, package your applications in containers and deploy them to Azure, AWS, Google Cloud, Kubernetes or your own servers.

  • Fast to deliver
  • Built to last
  • Secure from day one
11+years of building software for finance, IT and project teamsAbout the team
DevOps and CI/CD

Our DevOps and CI/CD services

Pipelines, containers and infrastructure as code that take every change from commit to production the same way, every time.

CI/CD pipelines

Every change built, checked and tested automatically before it is merged.

Discuss this service

What we cover: Any platform: Azure, AWS, Google Cloud, your own data centre or a single server. GitHub Actions, GitLab CI, Azure DevOps or Jenkins; Docker, Kubernetes or OpenShift.

The team behind PMC, trusted by
  • BNP Paribas
  • Allianz
  • Hexagon
  • Hewlett Packard Enterprise
  • Enapter
Solutions

DevOps solutions we set up

  • Small releases, every day

    Teams ship small changes daily instead of large releases every quarter.

  • A new environment per customer

    A complete environment for a new customer is created automatically, as for every PMC system.

  • Cloud migration

    Applications move from old servers into containers in the cloud, step by step.

  • Security checks in every build

    Dependencies and images are scanned for known vulnerabilities before they reach production.

Releases that still need a weekend and a checklist?

Walk us through your last release. We show you which steps a pipeline takes over and what it would cost to set up.

Plan your pipeline
A worked example

How a project like this runs.

Example

From manual deployment to a release pipeline

The situation

A web application with a .NET back end is deployed by copying files to a single server, and every release takes an evening and two people.

What we do
  1. We write down every step of today's release, including the ones nobody documented.

  2. A GitHub Actions pipeline builds, tests and scans every change.

  3. The application runs in Docker containers, with staging and production described in code.

  4. Production releases need an approval and can be rolled back in one click.

The result

Releases happen during the working day, with a record of who approved what.

An illustrative example of the way we work, not a named customer.

AI inside

AI in your delivery pipeline

Used where it helps engineers, checked like any other step.

  • AI-assisted code review
  • Log and error analysis
  • Alert summaries
  • Release notes drafts
  • Cost and usage insights
  • Runbook assistants
  • Infrastructure code suggestions
  • Dependency update proposals
  • Security findings explained
Why it pays

Why automate delivery

01

The same release, every time

Today
Releases built on someone's laptop and copied to the server by hand.
With it in place
Every release built, tested and deployed by a pipeline, the same way every time.
Safe releases

Fast releases that do not break things.

Speed only counts if production stays stable.

Nothing ships untested
A change reaches production only after its build, tests and security scans have passed.
A person approves production
Releases to production need an approval, and every one is recorded.
Secrets out of the code
Keys and passwords live in a secret store, never in the repository.
Always a way back
Every release can be rolled back in one click.
What you receive

Everything you need to own the result.

  • Pipelines in your repository, documented step by step
  • Docker images and environment definitions
  • Infrastructure as code for staging and production
  • Secrets moved into a secret store
  • A runbook for releases and rollbacks
  • Training for your developers on the new workflow

Is it right for you?

A good fit when
  • Software that is released by hand today
  • Teams that want to ship more often without more risk
  • A planned move to containers or to the cloud
Not the right fit when
  • Software that will not be changed again
Speed, quality and security

Fast does not have to mean fragile.

Every project is held to the same standard, whatever the service. It is the standard we build and run PMC to every day.

  • Fast to deliver

    Results in weeks, not quarters.

    • A working version at the end of every short cycle
    • Releases through an automated pipeline, not by hand
    • Small changes shipped often, so value arrives early
  • Built to last

    Software your team can still understand and change years from now.

    • Every change built and tested automatically before it is merged
    • Unit, API and end-to-end tests in a real browser
    • Documentation and a clean handover, or we run it for you
  • Secure from day one

    Security is part of the build, not a check at the end.

    • OWASP Top 10 and BSI IT-Grundschutz as the reference
    • Dependencies and images scanned for known vulnerabilities in every build
    • Access by role, changes logged, secrets kept out of the code
How we work

From manual releases to a pipeline you can trust.

  1. Review today's setup

    We look at how code is built, tested and released today, and where time and risk are lost.

  2. Build the pipeline

    Build, tests and security scans run automatically on every change.

  3. Containers and environments

    Applications run in containers, with staging and production described in code.

  4. Release with approval

    Production releases need an approval and can be rolled back in one click.

Servers only one person knows how to set up?

We describe them in code, put them in a pipeline and document them, so anyone on your team can rebuild them.

Review your setup
Ways to work with us

Choose how much of the work you hand over.

From one clearly scoped project to a team inside your business and the long-term running of what we built. Every model has one accountable partner: Virtual Eye.

  • For a defined result

    Fixed-scope project

    You know what you get before the build starts: a concept, a prototype and a fixed scope come first.

    • A workshop on your process and the result you need
    • Concept, prototype and fixed scope before production code
    • A working version at the end of every short cycle
  • When the problem is not yet clear

    Forward deployed team

    A small Virtual Eye team works inside your business, learns how work and money really move, and delivers the solution with your people.

    • One lead for management, plus the engineers who build
    • Outcome and scope agreed in writing
    • A demo every week
  • For software you already run

    Takeover and modernisation

    We take over an existing application, make it safe to change, then develop it further step by step.

    • What exists is documented and tested first
    • Stabilised before anything new is added
    • Further development in small, tested releases
  • After go-live

    Run and evolve

    We host, monitor, update and support your applications on our servers, in your cloud or on-premises.

    • Monitoring and alerts that go straight to our team
    • Backups, updates and security patches
    • Support and further development from the team that built it
Customers

What customers say about working with us.

Quotes about the Virtual Eye team from PMC projects: the same people who would work on yours.

“Well thought-out concepts, tailored precisely to us. Very competent and always friendly, even during the stressful implementation phase.”
Iris HummelManager Infrastructure Services Sales DACH, Hewlett Packard EnterpriseTranslated from German
“PMC provides valuable support in day-to-day business and the team is very reliable, serious and friendly!”
Hao LiCentral Project Office PMO, Allianz Global Corporate & Specialty SE
“As a customer from day one, we have found reliable, fitting solutions with Virtual Eye throughout the years. Above all, the fast and flexible service.”
Sebastian StepferExecutive Director Public Safety EMEA Region, HexagonTranslated from German
Tech stack

The tools we use for this.

We choose them for your systems and your team, and we document every choice.

Cloud platforms, infrastructure as code and pipelines that take every change safely to production.

Cloud platforms

  • AWS
  • Microsoft Azure
  • Google Cloud
  • DigitalOcean
  • Vultr
  • OVHcloud
  • Hetzner
  • IONOS
  • Open Telekom Cloud
  • Scaleway
  • Linode
  • Cloudflare

Infrastructure as code and automation

  • Terraform
  • Terragrunt
  • AWS CloudFormation
  • Ansible
  • Packer
  • Puppet
  • Chef
  • SaltStack

Containers and orchestration

  • Kubernetes
  • Docker
  • Red Hat OpenShift
  • Helm
  • Argo CD
  • Apache Mesos

Monitoring and observability

  • Prometheus
  • Grafana
  • ELK Stack
  • Datadog
  • Zabbix
  • AppDynamics
  • Splunk
  • Sentry
  • OpenTelemetry
  • Nagios

CI/CD

  • Jenkins
  • GitLab CI/CD
  • GitHub Actions
  • Bitbucket Pipelines
  • Azure DevOps
  • Bamboo
  • CircleCI
  • TeamCity
Your technology is not listed?

Tell us what you run. If we have not worked with it yet, we say so, and tell you how we would approach it.

Talk to our engineersSee all technologies
Industries we serve

DevOps for the industries we know

Years of PMC have taught us how these industries approve, buy, report and get audited.

Banks

Pipelines with approvals, signed builds and a record of every release.

  • Release approvals and audit logs
  • Security checks in every build
  • Separation of duties in the pipeline
Questions

Questions teams ask before they start.

Do we have to use GitHub?

No. We set up pipelines on GitHub Actions, GitLab CI or Jenkins, wherever your code lives.

Can you deploy into our own infrastructure?

Yes: Azure, AWS, Google Cloud, Kubernetes, OpenShift or a single server. Our own products run in several of these ways.

What if a release goes wrong?

Every release can be rolled back. Staging catches most problems first, and production deployments can wait for an approval.

How do you keep secrets safe in the pipeline?

Keys and passwords live in a secret store, never in the repository, and dependencies and images are scanned for known vulnerabilities in every build.

Can you move our applications to the cloud?

Yes, step by step: applications move from old servers into containers, through staging first and into production after approval.

Tell us what you want to build.

Describe the process, the systems involved and when it should go live. We reply with a first assessment and the next step.

Or write to us directly: hello@virtual-eye.com

What happens next?

  1. You write to us

    What you want to build, the systems involved and when it should go live.

  2. A first assessment

    We reply with a first assessment and the next step.

  3. A workshop

    On your process and the result you need, before any technology is chosen.

  4. A fixed scope

    A concept, a prototype and a fixed scope before the first line of production code.