What is included
- A scheduled provisional gap diagnostic. Work through browser-based Kubernetes incident simulations while the founder observes how you investigate.
- A private written report. Each sampled objective is reported as demonstrated, not demonstrated or insufficient evidence against a published rubric.
- Targeted practice. Short drills and incident practice are selected from what the report found, not added as a fixed pile of work.
- An unseen equivalent reassessment. A different incident samples the same objectives against the same rubric so you can compare what changed.
- Direct founder delivery. During the beta, every session is scheduled and graded personally, and every report is written by the founder.
The four-week loop
Provisional gap diagnostic
A scheduled 45–90 minute session using browser-based incident simulations, followed by your private objective-level report.
Practice aimed at the sampled gaps
Short drills and incident practice selected from the report. Assignments substitute for one another when needed to remain within the weekly ceiling.
Unseen equivalent reassessment
Investigate a different incident that samples the same objectives at a comparable level, then compare the rubric outcomes.
The loop can repeat with new material
Later work is chosen from the next sampled needs. New inventory is not automatically extra required work.
The weekly core loop has a hard 90-minute ceiling. It is composed from configured worst-case durations, not an average learner time. Optional material sits outside the advertised core work.
Who it is for
The founding beta is deliberately narrow. It is a good fit if you:
- are based in the UK during the beta;
- already work with Kubernetes workloads;
- understand the basic
kubectlworkflow; - are expected to investigate failures with growing independence;
- want specific feedback on your investigation process; and
- can set aside approximately 60–90 minutes a week.
It is not the right starting point if you are new to Kubernetes, mainly want CKA or CKAD exam preparation, need access to a hosted cluster, or want a credential. Start with the free Novice and Fundamentals pathways if you are still building the foundations.
How access works
There is no instant checkout. Requesting access starts a 15-minute fit-check both ways. The founder asks about the Kubernetes work you already do, you see what the session involves, and either side can decide it is not a match.
During the beta, access is opened manually for approved UK participants because every diagnostic and reassessment is scheduled personally.
Price, cancellation and guarantee
- £20 per month. There is no annual plan or separate paid tier in this offer.
- Cancel anytime. Access continues to the end of the paid subscription period.
- 30-day first-payment guarantee. The money-back guarantee applies to the first payment, under the published terms.
- Founding rate. The £20 monthly rate continues after the beta for as long as the subscription runs without a break.
- UK only during the beta. Free Labs remain available outside the UK.
The complete consumer terms are available before anyone is charged. Read the Terms of Service.
The honest boundary
These are browser-based simulations. They are not real or production clusters, and CloudCaive is not a certification, job guarantee or employer-recognised credential.
Your report describes only what the sampled session demonstrated under its stated conditions. It does not claim that you are ready for every incident, role or environment.
“Founding beta” means the scenario library and product polish are still growing. It does not weaken the core promise: a complete diagnose–practise–reassess loop, personally delivered, with a first-payment guarantee.
Complete FAQ
Who is the founding beta for?
UK engineers already working with Kubernetes who want specific feedback on how they investigate failures. You should know the basic kubectl workflow and be expected to troubleshoot with increasing independence.
What do I receive?
A scheduled incident session, a private rubric-based report, targeted drills and incident practice, and an unseen equivalent reassessment. Every beta report is written personally by the founder.
How much time does it take?
The advertised core work is composed to remain within approximately 60–90 minutes a week, with a hard 90-minute ceiling. Drills and incidents may substitute for one another; new material is not automatically additional required work.
Is the founding beta UK-only?
Yes. The paid beta is limited to the UK while its tax, terms, privacy treatment and founder-led schedule are validated. The free Labs pathways are available more widely.
Is this a real Kubernetes cluster?
No. The incidents are simulations in your browser. That removes setup and cloud cost and gives every participant controlled conditions, but it is not a production environment.
Is this a certification?
No. It is not a certification, job guarantee or employer-recognised credential. Reports make bounded claims about sampled objectives only.
Why not use an AI assistant?
AI can explain commands and suggest causes. CloudCaive controls the incident, observes the decisions you make before seeing an answer, maps them to a rubric and uses an unseen equivalent to compare performance.
Can I cancel and request a refund?
You can cancel anytime. The first payment has a 30-day money-back guarantee under the published terms, which are available before payment.
What happens to the £20 rate after the beta?
The founding rate continues while your subscription remains uninterrupted. Pricing for people joining after the beta will be reviewed separately.
I am new to Kubernetes. Where should I start?
Start with the free Novice and Fundamentals pathways in CloudCaive Labs. They assume no prior experience and build the foundations before incident assessment.