// service / consulting
Graylog consulting from people who run it
Before you buy hardware, sign a license or commit to an architecture — get an independent engineering view.
- format:
- time-boxed, written outcome
- inputs:
- metrics, configs, requirements
- output:
- recommendation + reasoning
- independent:
- no license or cloud commissions
- legal:
- not legal advice
- next.step:
- your team, or us
Consulting engagements are time-boxed and outcome-focused. You bring a question — "how big does this need to be?", "why are searches slow?", "do we need a cluster?", "which edition covers our requirements?" — and we come back with an answer you can act on and the reasoning behind it.
We are independent of Graylog, Inc. and of any cloud provider. We do not earn commissions on licenses or infrastructure, so recommendations are based on your workload.
// scope
Common consulting topics
Capacity & storage planning
Disk, memory and compute requirements from ingest rate, message size, retention, replicas and index overhead.
Architecture review
An assessment of an existing or planned design against your availability, security and growth requirements.
Retention design
Index sets and rotation strategies aligned with how long each class of log must be kept and searched.
Log pipeline design
What to collect, how to parse and enrich it, and how to route it into streams so it stays useful and affordable.
Edition evaluation
Mapping your requirements against Graylog Open and the vendor's commercial editions so you can make an informed licensing decision.
Provider selection
Cost and operational comparison of hosting options such as Hetzner, AWS, Google Cloud, Azure or your own hardware.
// deliverables
What you receive
- Written recommendations with assumptions made explicit
- Sizing model you can re-run as volumes change
- Reference architecture diagram
- Requirements-to-edition mapping (technical, not legal)
// faq
Common questions
How do you estimate Graylog storage?
Start from daily ingest volume, multiply by retention days and by (1 + replica count), then apply an index overhead factor measured from a sample of your own data. Add headroom for disk watermarks and growth. We build this model with your real numbers.
Can you tell us whether we need a commercial license?
We can map your technical requirements against the vendor's published feature comparison. The licensing decision and any legal interpretation remain with you and, where needed, your legal counsel or the vendor.
Do you only consult on Graylog?
Graylog is the focus, but the work covers the surrounding infrastructure: Linux, networking, storage, OpenSearch, MongoDB, collectors and automation.
// related services
Independent service provider — not affiliated with Graylog, Inc. Software licensing is subject to the applicable vendor license. Licensing notes.
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.