We review, change and maintain your cloud, DevOps and systems, and build cybersecurity into each service. Also custom development as an extra. Kubernetes is one of the rows under «Change»: migration and platforms, when it pays off.
Frequently asked questions
Everything clear before we begin.
Before we begin, everything should be clear: how we work, what we need from you, how we protect security and how to engage us. If you cannot find your question, write to us and we will answer it.
Find your answer
We start with a 30-minute call to understand your case. Then we send a written proposal with scope and deliverables before touching anything. Once agreed, we work in your accounts and repositories, validate the changes with you and document the decisions and procedures.
Moving workloads that run today on virtual machines or as standalone containers to Kubernetes, on AKS, EKS or GKE: an inventory of what runs and its dependencies, choice of cluster, manifests, Helm or Kustomize, and a release and cutover strategy. If you already have a cluster, we start from it; if not, we design it with you.
It depends on the workload and on how it is set up today. If a downtime window is needed, we agree it with you before acting and it is put in writing. We do not promise there will be no interruption without knowing your application.
Yes, if we agree it. We design, deploy and run; what we cover and during which hours is put in writing before we start. You can also keep the documentation and carry on with your own team or another provider.
Argo CD or Flux for GitOps, and manifests, Helm or Kustomize for deployment. If you already use one of them, we look at it on the first call.
For software companies, SMEs and scaleups when infrastructure starts to slow down what they want to do, with or without an in-house tech team. The problem matters more than the size of the company.
Context, not perfect documentation: what you have today (if you already have a cluster, on which provider; if not, which applications you want to move to Kubernetes), what you want to achieve and who decides. And one person on your side to answer technical questions and coordinate access.
No. We can design it with you or start from the one you already have.
It is not essential. What we do need is one person on your side as technical contact. What we deliver is documented so that whoever runs it afterwards can maintain and review it.
Yours. We work in your accounts, repositories and tools. The code, the infrastructure as code and the documentation stay in your company’s name, so you can carry on with your own team or another provider.
The minimum for the agreed scope, personal and temporary: through SSO or your provider’s roles, never with shared passwords. Whenever the scope allows, we start with read-only permissions. When we finish, we agree with you on removing the access.
No. Before any change in one of your environments we agree with you what changes and when, and we touch nothing without your explicit confirmation.
We do not store secrets in repositories or share them by chat or email: we use the secrets manager you already have or the one we agree with you. If you need a confidentiality agreement before we access your environment, we can sign one.
Yes, it is one of the seven areas: RBAC, policies, secrets, supply chain and hardening against the CIS Kubernetes guidance. The aim is a smaller attack surface and clearer access, in the cluster and in the delivery chain.
You book 30 minutes in the calendar on our website and tell us what you have and what you want to achieve. We tell you where we would start, with no commitment. If we are a good fit, the next step is a written proposal, before touching anything.
It depends on your environment and the scope, so we do not give figures or timelines without knowing it; the only published reference is the report of the cloud review (entry level) within 5 working days once access is granted. After the call we send you a written proposal with scope, deliverables and terms.
No. You can come with a specific need, such as an upgrade or cluster security, or with a whole platform. We scope it on the call and the scope is put in writing in the proposal.
We tell you in the first conversation and, where we can, point you to another option.
No. We work by diagnostic, fixed project or monthly plan with agreed hours; for a full-time role it’s better to hire someone in-house.
We work within hours agreed in writing. We do not offer 24x7 on-call or availability or response SLAs, and we tell you so from the start. We leave alerts and runbooks so your team, or an on-call provider, can act.
No. We apply reasonable means and show it: restores tested and recorded, reports with evidence. Savings are potential until they are applied and measured.
Everything is documented and there is an exit plan from the start.
We work with the minimum access needed and, wherever possible, inside your own accounts. If our work involves access to personal data, we first sign a data processing agreement with you. We point out which technical points may affect GDPR or, if it applies to your organisation, the ENS (Spain’s National Security Framework); we do not give legal advice: the final assessment is yours or your adviser’s.
With AWS, Azure and Google Cloud. Providers are platforms; our services answer to your need, not to a provider.
The first call is 30 minutes with no commitment; then, the scope in writing. As a published reference: the report of the cloud review (entry level) within 5 working days once access is granted.
We could not find an answer matching those terms.
Your question may need its own answer
Describe your environment, the blocker and the goal you need to reach. We will reply with a clear first assessment.