Two choices you
only make once.
Two choices determine how your service is set up: does the platform run with us or with you, and do you share an environment or get your own tenant. They decide who can reach what, how your data stays separated, and what a move costs later. That is why we settle them up front rather than along the way.
Hosted Splunk.
We deliver and run the complete environment, so you do not have to think about infrastructure, operating systems or version management.
- Platform, infrastructure and operating system managed by us
- Monitoring, patching, upgrades and capacity steering included
- One invoice and one point of contact for the whole chain
When Splunk is critical but running it is not your core business. You buy availability, not a construction kit.
Discuss Hosted SplunkRemote Management.
The infrastructure stays yours, in your data centre or cloud. We manage, optimise and support the Splunk platform running on it.
- You keep ownership of hardware, network and cloud contracts
- We handle platform management, changes, upgrades and optimisation
- A clear split of responsibilities, recorded in the service agreement
When infrastructure has to stay in house for policy or compliance reasons, but you do not want to build the Splunk specialism yourself.
Discuss Remote ManagementMulti or single tenant.
Two ways to set up your environment. The choice is about governance and speed, not about quality: both are fully supported.
- Multi tenant, efficient and quick to onboard, with data, configuration and rights logically separated within a shared technical base
- Single tenant, a dedicated environment with maximum control and room for customisation, for specific governance or security requirements
- Switching later is possible but means a migration, so we discuss it up front
Three questions: do you have requirements that only a dedicated environment can meet? How quickly do you need to go live? And how much customisation do you expect in the first two years?
Discuss the setupWhat it means in practice.
| Who runs the infrastructure | Hosted: we do · Remote: you do |
| Who runs the Splunk platform | We do, in both cases |
| Where the data sits | Hosted: with us · Remote: with you |
| Speed of getting started | Multi tenant: weeks · Single tenant: longer |
| Room for customisation | Single tenant: maximal · Multi tenant: within the shared base |
| When single tenant | With specific governance, security or architecture requirements |
In doubt? Then multi tenant is usually the sensible start. Moving to single tenant later is possible; the other way around is rarely worth the effort.
Do you already know where your data is allowed to live?.
That is more often a governance question than a technical one. We are happy to think it through before you commit.