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

IT solutions

Your systems up, patched and backed up. Without the worry.

We host, monitor and look after your applications and servers, with backups, updates and certificates, and a team you can call when something needs attention.

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

Our IT solutions

Hosting, monitoring, backups, updates and support from one team with a named contact, for what we built and what you already run.

Managed hosting

Your applications on servers we run, in your cloud or on your own hardware.

Discuss this service

What we cover: Hosting, monitoring, backups, updates and support for your systems, in our infrastructure or yours. Response times are agreed in your contract.

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

What we run and support

  • Run what we build

    Applications we develop are hosted and looked after by the same team.

  • Take over existing systems

    We document, stabilise and take over the operation of applications built by others.

  • Remote support

    With the user's consent, our support team joins their screen and solves the problem directly.

  • Microsoft 365 and Azure

    Accounts, permissions and Azure resources set up and kept in order.

Nobody really owns the servers any more?

Give us a list of what runs where. We tell you what we would watch, back up and update, and how we would take it over.

Talk about operation
A worked example

How a project like this runs.

Example

Taking over an application from another supplier

The situation

A business application runs on a server set up years ago by a supplier who has since left, with no documentation and no tested backups.

What we do
  1. We document the server, the application, its accounts and its backups as they are.

  2. Monitoring, tested backups and a patch schedule are set up before we take responsibility.

  3. Hosting moves to an environment we run, in an agreed time window.

  4. Support runs through a ticket system, with a named contact and agreed response times.

The result

The application runs on a documented, monitored setup with backups that are known to work.

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

AI inside

AI in operation and support

To spot problems earlier and answer users faster.

  • Alert summaries
  • Log analysis
  • Support assistants
  • Usage and cost reports
  • Runbooks as assistants
  • Microsoft 365 Copilot setup
  • Ticket triage
  • Capacity forecasts
  • Access reviews prepared
Why it pays

Why hand operation to us

01

Problems seen before users call

Today
Outages noticed when users call.
With it in place
Problems seen by monitoring first, and our team alerted.
Operations

Problems found before your users find them.

What you can expect from us every day your systems run.

Watched around the clock
Availability, errors and certificates are measured automatically, and alerts reach our team first.
Restores that are tested
Backups are restored on a schedule, so we know they work before you need them.
Patched on a fixed schedule
Security updates go in on a fixed schedule, urgent ones straight away.
Response times in writing
How fast we react is agreed in your contract, not just promised on a website.
What you receive

Everything you need to own the result.

  • Documentation of every system we run for you
  • A monitoring dashboard you can look at yourself
  • Tested backups and a record of every restore
  • A schedule for updates and certificate renewals
  • A ticket system and a named contact
  • Regular reports on incidents and changes

Is it right for you?

A good fit when
  • Applications without a team that looks after them
  • Servers and certificates handled when someone has time
  • Software we build, run by the same team
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 handover to quiet operation.

  1. Take stock

    We document your applications, servers, accounts and backups as they are today.

  2. Stabilise

    Monitoring, backups and updates are set up before we take over responsibility.

  3. Take over operation

    Hosting, updates and support move to us, with a named contact.

  4. Run and report

    Incidents and changes are reported, and response times follow your contract.

Systems someone else built, and nobody documented?

We take them over, document them and keep them running, with a named contact for your team.

Plan a takeover
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

IT operation for the industries we know

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

Banks

Operation with documented changes, tested restores and clear responsibilities.

  • Monitored, documented hosting
  • Tested backups and restores
  • Change records for audit
Questions

Questions teams ask before they start.

What does managed hosting include?

Servers, backups, updates, certificates and monitoring, plus support when something needs attention. Scope and response times are agreed in the contract.

Can you take over applications we already have?

Yes. We document and stabilise them first, then take over their operation.

How does remote support work?

With the user's consent, our support joins their screen. Viewing and control are separate permissions, and the user can end the session at any time.

How do you know the backups work?

Backups are restored on a schedule, so we know they work before you need them.

How quickly do you respond?

Response times are agreed in your contract. Monitoring alerts reach our team first, so many problems are handled before your users notice them.

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.