CASES & EVIDENCE

What we do is easier to understand when you see the context.

We publish experiences with the real scope of the work, without turning qualitative feedback into invented metrics or presenting internal technical evidence as client outcomes.

FEATURED CASENexure.aiPreparation and support for an application deployment into production.View case

Three kinds of evidence, each proving something different

EXPERIENCES

What existed, what we did and what remained afterwards

CLIENT · DEPLOYMENTNexure.ai

“They supported us throughout the application deployment process, showing great dedication and professionalism. We are very satisfied with the team’s work and the results achieved.”

From a finished application to an environment ready to operate.

STARTING POINT

Starting point

The application was ready, but it lacked a consistent operational foundation for production.

WORK DELIVERED

Work delivered

Docker installation and configuration, Ubuntu server hardening, container setup, deployment and technical support.

OUTCOME

Outcome

A more secure and operable environment, together with a clearer deployment process for the client.

TECHNICAL EVIDENCE · CLOUD ARCHITECTURENubyron technical case

“The important decision happens before Terraform. Infrastructure as Code makes architecture reproducible, but it can also reproduce unnecessary complexity.”

From a complex flow to a simpler, observable architecture on Azure.

STARTING POINT

Starting point

Logic Apps, several chained Azure Functions, frequent polling and a Terraform base that was difficult to evolve.

WORK DELIVERED

Work delivered

Event-driven redesign with Event Grid, compute consolidation and clearer separation of modules by responsibility.

OUTCOME

Outcome

A simpler, more observable and maintainable flow with fewer dependencies between components.

ANOTHER CLIENT EXPERIENCE

Service quality also shows when something unexpected happens

CLIENT · CONTINUITY

Responding when the problem was not on the calendar.

A non-profit association valued the rapid response to a website problem during a public holiday.

— Non-profit association

PARTNERS AND COLLABORATORS

How others describe the way we work

These comments are about collaboration and judgement. We do not present them as client case studies.

“If a company needs specialist Kubernetes support, I would recommend speaking with the Nubyron team. Its value proposition is solid and especially distinctive because of how it works.”
Leafar MainaFounder & CEO · CLM Cloud Solutions

“I would highlight Nubyron’s support with talent acquisition and its ability to work with Human Resources processes, not only technical stakeholders.”
Jorge Ardá CabezaTaisa

HOW WE PUBLISH EVIDENCE

One simple rule: describe exactly what happened

WITH PERMISSION

With permission

Names, logos and quotations are shown only when publication is authorised.

WITH CONTEXT

With context

We distinguish one-off work, projects, recurring support and operations.

WITHOUT INFLATION

Without inflation

We do not turn qualitative feedback into unconfirmed percentages, savings or SLAs.

WITH BOUNDARIES

With boundaries

We explain what we did, what was outside scope and which responsibilities each party retained.

Want to know what is worth reviewing in your platform?

Tell us what is happening. We will review the context before proposing a service or project.

Tell us what is happening