FREQUENTLY ASKED QUESTIONS
What matters before we start working together
No fine print or commercial jargon. Here we explain how we operate, what we require, and where our technical boundaries lie.
Scope & DiscoveryDo I need to know which service to contract before speaking with you?
Do I need to know which service to contract before speaking with you?
No. You can start by explaining what is currently happening: recurrent downtime, deployment bottlenecks, uncontrolled cloud expenditure, unstable Kubernetes clusters, or architectural decisions you need to validate. With that context, we guide you towards an audit, a fixed-scope project, or continuous platform support.
Operations & PlatformsDo you work with companies outside Spain?
Do you work with companies outside Spain?
Yes. Nubyron is headquartered in Gran Canaria and operates 100% remotely with scaleups and enterprises across Spain, Europe, Latin America, and the United States. We agree on coordination time zones, direct communication channels (Slack/Teams), and response expectations beforehand to ensure smooth collaboration.
Scope & DiscoveryWhat if our infrastructure is messy or poorly documented?
What if our infrastructure is messy or poorly documented?
That is the most common scenario and where we deliver the highest immediate value. You do not need to clean up the environment prior to contacting us. We start with a discovery phase to map the actual production state, highlight critical security or availability risks, and prioritise the most impactful improvements.
Models & TermsDo you enforce vendor lock-in or mandatory retainers?
Do you enforce vendor lock-in or mandatory retainers?
No forced lock-in. We offer fixed-scope engagements with well-defined deliverables and milestones, as well as monthly continuity agreements focused on technical targets. Long-term partnerships should be built on technical results and mutual trust, not restrictive clauses.
Access & SecurityWhat access do you require to operate?
What access do you require to operate?
Only the strictly necessary permissions adhering to the Principle of Least Privilege. We require named, revocable, and auditable credentials in your cloud providers and source code repositories. Any action on critical production workloads is coordinated and approved in advance.
Access & SecurityDoes the infrastructure need to reside in Nubyron accounts?
Does the infrastructure need to reside in Nubyron accounts?
Absolutely not. We always operate inside your own cloud accounts (AWS, GCP, Azure, OCI), your repositories, and your tooling. Ownership, access governance, Infrastructure as Code (IaC), and all intellectual property remain 100% in your hands.
Scope & DiscoveryHow do you initiate a project or partnership?
How do you initiate a project or partnership?
We follow a disciplined four-stage method: discover the real system without altering production; agree on scope, deliverables, responsibilities, and boundaries; execute changes in visible and tested iterations; and systematically transfer runbooks and capabilities to your internal team.
Models & TermsDo you replace our internal software engineering team?
Do you replace our internal software engineering team?
No. We do not place profiles or replace the product team. We take responsibility for a defined Cloud, Platform Engineering, DevOps or SRE problem, work alongside your team and leave the documentation and knowledge behind.
Operations & PlatformsDo you include 24/7 on-call rotation or monitoring support?
Do you include 24/7 on-call rotation or monitoring support?
Continuous observability and operational SLAs are explicitly defined within dedicated operations packages. Architectural engagements, assessments, or migrations do not include 24/7 on-call coverage by default unless specifically contracted.
Operations & PlatformsDo you work exclusively with AWS, Azure, or Kubernetes?
Do you work exclusively with AWS, Azure, or Kubernetes?
No. We have extensive production experience across AWS, Google Cloud (GCP), Microsoft Azure, and Oracle Cloud (OCI), as well as enterprise Kubernetes, Linux servers, and hybrid architectures. Tooling is selected based on the business problem, never the other way around.