TEQcloudServices
One thing, done properly: Kubernetes operations.
We run the cluster you already have. No hosting, no app development, no scope creep. Just the boring, important work that keeps production up.
What we actually do
The day-to-day of keeping a production cluster healthy.
Health checks
Regular reviews of cluster state, resource usage, certificate expiry, and security posture. Weekly or monthly depending on your plan.
Upgrades & patching
Control plane and node upgrades planned, tested, and executed. A critical CVE in something we run gets patched out of band, outside the scheduled window.
Monitoring & alerts
Prometheus, Grafana, Alertmanager, or your existing stack. We tune the noise so alerts mean something.
Incident response
When something breaks during the window your plan covers, we pick up the kubeconfig and fix it. Then we write down what happened.
Networking, ingress, certificates
cert-manager, ingress-nginx or Traefik, internal DNS, NetworkPolicies. The plumbing that needs to keep working.
RBAC & secrets
Least-privilege roles and secret rotation, applied on request and watched for expiry. Not glamorous, but it is what stops the bad days.
Who this fits
If you recognise yourself below, we should probably talk.
You already run on K8s, but nobody on the team is paid to be the Kubernetes person. Things mostly work, until they do not.
Hiring a senior DevOps engineer at €80k+ is not yet justified, but the founder is tired of being on call for ingress.
You run K8s in your own datacentre or a private VPS for data-residency reasons. You want operations expertise without moving the workload.
Process
How starting works
Intake call
Half an hour, no slides. We talk about your cluster, your team, and what is keeping you up at night.
Cluster audit
We get read-only access and produce a short written report: what is healthy, what is risky, what to fix first. Fixed price, no obligation to continue.
Onboarding
We agree on a plan, set up access, alerting, and the contact channel. You meet the person who will be doing the work, also the person you just talked to.
Ongoing operations
Monthly cadence, retainer hours, and a written account at the end of the month that scales with your plan. Cancel any time with one month notice.
What we do not do
Being clear about scope up front saves both of us a meeting.
We do not host your applications
Your cluster runs on your cloud account or your hardware. We have no infrastructure to lock you into. If you part ways with us, you keep everything.
We do not offer 24/7 support
We work business hours. If you need genuine 24/7 on-call, you need an in-house team or a much larger managed-service provider. We will tell you that during the intake.
We do not build your application
We manage the runtime, not what runs on it. Writing your product, building your container images and authoring your Helm charts is not our job.
Sounds like a fit?
Pricing is on the next page. Or send a short email and we will reply with honest questions.