You hold the framework. We run the platform.
Public-sector framework contracts invite every holder to bid on every work package, operations included. Most holders win the integration and application work and pass on the operations package, because running a platform around the clock is not what they do. That package does not have to go to someone else's framework.
VSHN operates the OpenShift platform as your subcontractor, under your contract with the buying office. You stay the single point of contact for the client. We stay in the background, operating what we are certified to run.
Why this is a different arrangement than our other partnerships
Our partner program is built for consultancies delivering alongside VSHN on a direct engagement. A framework holder's situation is narrower: you have already won the right to bid, the buying office already knows your name, and what is missing is the operations capability to take the package rather than decline it.
- You keep the contract. The buying office's relationship stays with you. VSHN operates underneath it as subcontractor, not as a competing bidder.
- VSHN does not hold a framework contract of its own. We are not bidding against you, and we do not claim to hold any public-sector framework. What we bring is 24/7 OpenShift operations, Swiss data residency and a 99.99% SLA as Red Hat Premier CCSP, for you to offer under your own name.
- The shape of the arrangement, not one framework's numbers. Subcontracting terms differ by framework: most require the buying office's written consent before a subcontractor is brought in, and some cap how much of a package can be subcontracted. Read your own framework's terms; this page describes the arrangement, not any specific framework's figures.
What this covers and what it does not
- No customer or framework name appears on this page, or anywhere else on this site, without that party's written consent.
- We will not advertise a collaboration that a framework's own confidentiality terms bar us from naming. If your framework restricts naming a subcontractor's role, that restriction holds here too.
- This is about operations work packages specifically. Where you already run your own 24/7 operations on the platform a client needs, there is nothing for us to add.
Division of labor
| Your role | VSHN's role |
|---|---|
| Holds the framework contract and the buying office relationship | OpenShift cluster operations, as your subcontractor |
| Bids and wins the work package | 24/7 operations, monitoring, and incident response |
| Single point of contact for the buying office | Upgrades, security patching, and backups |
| Invoicing under the framework's own terms | SLA with Swiss data residency by default |
Talk it through before you bid
If a work package includes operations you cannot staff, we can work out the subcontracting shape before the bid goes in, not after you have already committed to terms you cannot deliver.