FREQUENTLY ASKED QUESTIONS

What matters before we start working together

No fine print or sales answers. Here we explain how we usually work, what we need and where the boundaries are.

01Do I need to know which service to buy before contacting you?

No. Start by telling us what is happening: incidents, deployments, costs, Kubernetes, lack of time or a technical decision you need to review. With that context we can guide you towards an assessment, project or recurring support.

02Do you work with companies outside Spain?

Yes. Nubyron is based in Gran Canaria and works remotely with teams in Spain and other markets. Before starting, we agree communication channels, coordination hours and response expectations to make sure the collaboration is workable.

03What if our infrastructure is messy or poorly documented?

You do not need to prepare the platform before speaking with us. We can start by understanding the current state, identifying risks and prioritising what deserves attention first. The scope depends on what we find and what you want to achieve.

04Do you require long-term lock-in?

We do not apply one general lock-in rule to every service. Some engagements are fixed-scope and others are monthly support. Duration, renewal, notice and specific conditions are agreed before work starts and depend on the service purchased.

05What access do you need?

Only the access required for the agreed work, following least-privilege principles where possible. We prefer named, revocable and auditable access. If a task requires especially sensitive information or permissions, we review it with the client first.

06Does the infrastructure need to be in Nubyron accounts?

No. Our preference is to work in the client’s own cloud accounts, repositories and tools so ownership and control remain with the client. If a project needs a different setup, it should be explicitly agreed and documented.

07How do you start a project or engagement?

We first understand the problem and enough context to avoid working blindly. Then we agree scope, responsibilities, priorities and boundaries. Only after that do we start making changes.

08Do you replace our development team?

Usually not. Nubyron focuses on Cloud, DevOps, SRE, infrastructure and technical operations. We work alongside product or development teams, covering the agreed area without automatically taking on application development responsibilities.

09Do you include monitoring, on-call or 24/7 support?

Only when those are explicitly part of the contracted service. An hourly support package, project or technical assessment does not automatically include continuous monitoring, SLAs, on-call or 24/7 coverage.

10Do you only work with AWS, Azure or Kubernetes?

No. We work with different platforms and tools depending on context. Technology should not be selected before the problem is understood. When a specific solution is not a good fit or falls outside our expertise, we prefer to say so clearly.

Does your question depend on your specific situation?

Tell us what is happening. You do not need to choose a service or prepare a proposal before contacting us.

Tell us what is happening