Nearvic · Freelance DevOps, Cloud & Security Engineering
Nearvic builds CI/CD pipelines, cloud architecture and the security controls that hold under regulation — deployment automation and GitOps, Kubernetes at fleet scale, and DevSecOps pipelines with real security gates — across AWS, Azure and Oracle Cloud. A freelance DevOps engineering practice, founder-led, remote-first and working internationally.
What Nearvic does
Every engagement starts with a discovery call and ends with a written scope. No exceptions — that's how infrastructure work stays predictable for both sides.
CI/CD pipelines built from scratch or rescued from sprawl — GitOps delivery, deployment automation, infrastructure as code, and the golden paths that let teams ship without filing a ticket. Automation comes first; security and reliability are built into the same pipeline, not bolted on after.
Reference architectures, multi-cloud design and platform decisions across AWS, Azure and Oracle Cloud — capacity planning, cost modelling and vendor-neutral advice shaped by production experience, not by whichever vendor sponsors the workshop.
Assessment, target architecture and execution for moves from on-premises or VMware onto AWS, Azure or OCI. Multi-account structure, network design, identity baseline, cost guardrails, and a cutover plan you can hand to an auditor.
Production-grade clusters, GitOps delivery, reusable Terraform modules and an internal developer platform, so teams provision what they need themselves with the guardrails already baked in.
Security gates inside the pipeline instead of bolted on after: IaC scanning, container and dependency analysis, secrets management, policy-as-code, and compliance automation for SOC 2, PCI DSS and ISO 27001 — evidence collected continuously, not the week before an audit.
SLIs, SLOs and error budgets that mean something. Observability across logs, metrics and traces. Incident response, blameless postmortems, capacity planning and tested disaster recovery — not a DR document nobody has opened.
Why Nearvic
The pitch is simple: we build the systems, not just the audit findings about them. That's a different kind of trust than a report can earn.
We implement what we recommend. Terraform, Kubernetes, CI/CD, security controls — all built into the platform we hand over, not a report describing someone else's.
Production experience across AWS, Azure and Oracle Cloud, including a sovereign-cloud deployment run to national data-residency rules. Advice that isn't shaped by which vendor happens to sponsor it.
Banking and fintech platforms, PCI DSS and SOC 2 controls, zero-trust access models — work done under the kind of compliance pressure that catches shortcuts.
Policy-as-code, GitOps and compliance automation instead of manual checklists and quarterly spreadsheets — controls that hold because a pipeline enforces them.
Trust & verification
Nearvic is founder-led today — that's stated plainly in the terms below, not papered over. Here's how to verify what's said here before engaging.
18 cloud and platform certifications across AWS, Azure and Oracle Cloud, each linked to the issuer's public verification page — see the founder's credentials.
Every engagement is confidential from the first call. Client names are withheld — you get the same treatment, permanently.
Real case studies — banking, sovereign cloud, GPU compute, platform engineering — with outcomes you can ask about on a call. See the work itself.
Direct quotes from people who've shipped alongside our founder are on the profile page.
Engagement
Infrastructure work fails on process more often than on technology. These are the terms Nearvic works under, before anyone writes a line of Terraform.
Questions
If your question isn't here, it belongs in the discovery call, not guessed at on a page — just ask.
Not yet — Nearvic is a founder-led practice today, not a registered legal entity. We say so plainly rather than imply otherwise. Where procurement requires a registered supplier, engagements run through your existing contractor-management or employer-of-record provider — see Engagement.
Yahia Mohamed Benabbou, personally, on every engagement today. Nothing here implies a team that doesn't exist — see his full background at profile.nearvic.com.
A discovery call, then a written scope — deliverables, milestones, and a fixed price or day rate — agreed before any work begins. No scope, no start.
Yes. That's the standard path today given the point above, and it's how most larger clients onboard an independent contractor without a registered local entity.
Yes, always, before any architecture, code or infrastructure details are shared — not after. Every past engagement was handled the same way; client names are withheld permanently as a result.
Every certification links to the issuer's public verification page, and the real case studies behind the numbers are documented in full — see credentials and work on profile.nearvic.com.
Contact
We reply to every serious enquiry within one working day. If the problem is outside what Nearvic does well, we will say so and point you somewhere better.