Neutral infrastructure

When two parties build something together, we provide the infrastructure as a neutral third party. Both sides work on it as equals, and neither can lock the other out.

Whose servers does it run on?

Two parties build something together, and an awkward question arrives at once. Whoever provides the servers holds the keys, and with them a lever that has nothing to do with the collaboration itself.

Whose servers does it run on? Two parties build something together, and an awkward question arrives at once. Whoever provides the servers holds the keys, and with them a lever that has nothing to do with the collaboration itself.

Both sides place their part with us Source code, data, keys: whatever the joint project needs sits on infrastructure that belongs to neither side. Servers, database and storage are with us.

As equals, with every access recorded Both sides work with the same rights. Neither can lock the other out, and every access is logged. Operation, backups and monitoring run on our side.

What happens at the end is settled at the start Release, transfer and separation are agreed in the contract before they are needed, not in the moment things escalate. We carry out what was agreed there.

What we provide

The infrastructure itself

Servers, database and storage sit with us, not with either party. That is the heart of it: as long as the technology belongs to one side, so does the switch.

Equal rights, an unbroken trail

Both sides get equal access. Every access is logged, not out of suspicion, but so that in case of doubt what happened can be read up rather than argued over.

The rules before they are needed

Release, transfer and separation are settled in the contract up front. The right moment to sort that out is the start of a project, not the day the parties fall out.

Running it day to day

Operation, backups and monitoring are included. A neutral party that nobody maintains is not a neutral party, it is an outage waiting to happen.

When this is needed

Two companies build a product together and neither wants it running on the other’s servers.
A client does not want to depend on a contractor granting them access.
Several partners run a shared platform and need a neutral place for it.
A collaboration ends, and the handover should be orderly rather than contested.

Common questions

Who owns the servers?
We do. That is the whole point: if they sit with one of the two parties, that party holds a lever that has nothing to do with the matter at hand. With us, neither side does.
What happens if we fall out?
What happens then was settled while the parties still agreed. We carry out what was agreed. That is why this question belongs at the start of a project.
Can we take over running it later?
Yes. The transfer is part of the arrangement and is settled up front, not negotiated afterwards.
Does that make you a stakeholder in our project?
No. We provide and run the infrastructure, nothing more. Neutral also means having no stake in the outcome.

Does this fit your situation?

A twenty-minute conversation usually settles whether a neutral party is the right route, and what it would need to cover in your case.

Discuss a project Back to the home page