FREQUENTLY ASKED QUESTIONS
What matters before we start
How we fit into your team, which responsibilities we can own and how we protect your control of the platform.
Fit and scope
We begin with the real problem and agree a clear responsibility before touching the platform.
When does it make sense to work with Nubyron?
When infrastructure starts slowing the product team down: fragile releases, unclear cloud spend, recurring incidents, Kubernetes debt or uncertainty around a migration. We can diagnose, build or support operations depending on your current situation.
How do you decide where to begin?
We review technical context, business impact and team constraints. If the problem is not yet bounded, we begin with diagnosis and priorities. If the outcome is clear, we define scope, deliverables, dependencies and acceptance criteria.
Can you work with an undocumented platform?
Yes. Infrastructure often grows faster than its documentation. We reconstruct the map from accounts, repositories, pipelines and conversations with the team, leaving useful decisions and runbooks as we progress.
What happens when work appears outside the agreed scope?
We make it visible, together with its impact and alternatives. We do not add silent changes: we agree whether it replaces another priority, becomes a later phase or requires an explicit extension.
Security and control
The client retains accounts, repositories, knowledge and decision-making power throughout the engagement.
What access do you need to our infrastructure?
Only what the agreed scope requires. We favour named identities, least privilege, temporary access, SSO and auditability. We avoid shared credentials and review access revocation at the end of each phase.
Who owns the code and documentation?
Your company does. Infrastructure code, manifests, pipelines, dashboards, architecture decisions and runbooks are created in repositories and tools controlled by the client.
How do you handle secrets and sensitive data?
We do not place secrets in code or documentation. We use the client’s existing secret managers and controls, minimise data exposure and agree any access to sensitive environments or information in advance.
Does the solution create a dependency on Nubyron?
Our aim is to reduce it. We favour maintainable standards, readable automation, operational documentation and knowledge transfer so the team can work with us and after us.
Working with your team
Senior engineers integrated into existing workflows, with direct communication and visible decisions.
Do you replace the internal development team?
No. We own the Cloud, Platform and SRE layer that needs specialist depth, while the internal team retains product knowledge and participates in decisions that affect how software is delivered.
How do you coordinate day to day?
We adapt to the team’s channels and tools: repositories, pull requests, work boards and technical sessions. We define owners, cadence and decision mechanisms without adding ceremonies that provide no value.
Which platforms and tools do you work with?
We work with AWS, Azure, Google Cloud and Oracle Cloud; managed Kubernetes and OpenShift; Terraform and OpenTofu; GitHub, GitLab, Argo CD and Flux; and observability stacks built around Prometheus, Grafana, OpenTelemetry or Datadog. If a technology falls outside our real experience, we say so at the start.
Do you work with distributed or international teams?
Yes. We operate remotely from the Canary Islands and collaborate in English and Spanish with distributed teams. We agree overlap windows, escalation channels and asynchronous documentation so location does not become a dependency.
Does your case need more than a generic answer?
Tell us what is happening. An engineer will review the context before suggesting the next step.