// service / managed infrastructure

Managed Graylog infrastructure, operated by engineers

You use Graylog. We keep the servers, search cluster, database, certificates, backups and upgrades underneath it in good shape.

graylog-managed-services.yaml
tenancy:
dedicated per customer
location:
your account or your servers (preferred)
access:
least privilege, auditable
changes:
planned, documented, reversible
support:
scope and response times per agreement
exit:
full documentation and code handed over

Logging platforms tend to degrade quietly: indices grow faster than planned, a certificate expires on a Sunday, a collector stops shipping and nobody notices until the incident where those logs were needed. Managed infrastructure means someone is watching those signals and acting on them.

Each managed environment is dedicated to one customer and preferably runs in your own cloud account or on your own servers, so you keep ownership of the data and the infrastructure. We are not a shared multi-tenant Graylog SaaS. Software licensing follows the Graylog edition you use; see the licensing section for what that means.

// scope

What we operate

01

Health monitoring

Node health, journal utilisation, processing and output rates, search cluster status, disk watermarks, MongoDB replication and certificate expiry.

02

OS & platform patching

Scheduled security updates for Linux hosts, container images and dependencies, with a rollback plan.

03

Graylog upgrades

Planned upgrades between supported versions following the vendor's upgrade notes, tested before production.

04

Capacity management

Tracking ingest growth and retention against disk and compute headroom, with recommendations before limits are reached.

05

Backup verification

Backups that are restored on a schedule — not just created.

06

Troubleshooting

Investigating failed inputs, stuck processing, slow searches and search cluster issues as they arise.

// deliverables

What you receive

  • Monitoring and alerting for the platform itself
  • Monthly operational summary: capacity, incidents, changes
  • Maintained infrastructure code and runbooks
  • Upgrade plan aligned with the vendor's support timelines
  • Clean exit path — nothing proprietary that locks you in

// faq

Common questions

Is this a Graylog SaaS?

No. We operate dedicated Graylog environments for individual customers, preferably in the customer's own cloud account or data center. We do not run a shared multi-tenant Graylog service, and we are not affiliated with Graylog, Inc.

What response times do you offer?

Support scope, hours and response targets are defined per agreement based on what your environment needs. We do not publish generic SLA figures that may not match your situation.

Can we keep admin access ourselves?

Yes. You own the environment. We work with named, auditable access that you can review or revoke.

You have logs. We build and operate the infrastructure that makes them useful.

Tell us about your environment. An engineer will reply with a first architecture outline.