Services
Web applications and internal tools, AI agents wired into systems that already run, cloud infrastructure on AWS and Azure, deployment pipelines, IT and security audits, and cloud bills brought back down. Code7 Information Technology is the day job; this is the same work taken on directly, for businesses in Saudi Arabia, India and remotely.
Six things, and they overlap more often than not — an audit turns into a migration, a build turns into a pipeline. Priced per engagement, scoped in writing first.
Web applications, internal tools, dashboards, booking and ordering flows, APIs and mobile-ready builds — designed, built, deployed and kept running.
Discovery and a written scope
Design, build and deployment
A handover you can run without me
Agents and automations wired into the systems a business already runs: support and back-office workflows, document and data handling, internal copilots, with integrations and guardrails.
The workflow mapped before anything is built
Integrations into the systems already in use
Guardrails, logging and a human step where it matters
Architecting, migrating and operating AWS and Azure environments — networking, compute, storage, backups and monitoring.
Architecture and migration plan
Networking, compute, storage, backups
Monitoring and alerting someone actually reads
Build and release pipelines, environment parity, deployment automation, and scripted operations that remove manual steps.
Build and release pipelines
Environment parity, staging to production
Rollback and deployment runbooks
Access control, secrets handling, hardened servers and VPN, plus the wider estate: identity, workspace tooling, vendor sprawl and licence waste.
Access, identity and secrets reviewed
Servers and endpoints hardened
A findings document with priorities, not a scan dump
Idle compute, duplicate storage, overlapping hosting and legacy vendor billing — found, verified, switched off.
Every running resource traced to an owner
Idle, duplicate and legacy spend listed
Savings verified with your team before anything is switched off
Two markets, and they are not the same engagement. In Saudi Arabia I am here — same working week, on site in Jeddah. In India I am from Kerala and work on your hours, remotely. Each has its own page because each has its own answers.
I live in Jeddah and work here. That is the practical difference: same working week, same hours, and close enough to be in the room when being in the room is what a problem needs. Lead DevOps Engineer and Technical Lead at Code7 Information Technology by day; the same work — cloud, pipelines, IT audits, applications and AI agents — taken on directly for other businesses in the Kingdom.
I am from Kerala, and a good part of what I have built was built for Indian businesses — fifteen or so production websites and applications, most of them for founders who needed the thing to work rather than a deck about it. I now work from Jeddah, which puts me two and a half hours behind you and inside your working day.
You have systems that grew one tool at a time and nobody whose job it is to hold them together. The first engagement is usually an audit, not a build.
The application exists and deployment is manual and frightening. Pipelines, environments and monitoring go in before the next hire does.
Good engineers waiting on infrastructure. I take the cloud, the pipeline and the access model off their plate.
Some of this work is a job, not a project. If that is what you are reading for, the experience is on the home page and the enquiry form takes it.
01
A paragraph is enough. I reply myself, usually within a working day, with the questions I need answered.
02
What is included, what is not, what it costs and how long. Nothing starts before that is agreed.
03
You see progress as it happens rather than at the end. Findings arrive as they are found, not saved for a reveal.
04
Documentation, access, runbooks. The point is that it keeps running whether or not I am still on it.
Both. I am based in Jeddah, Saudi Arabia, work across Saudi Arabia and India, and take remote engagements anywhere the time zones overlap enough to be useful.
It depends on scope, and I quote a fixed number before anything starts rather than billing an open hourly rate. An audit is the cheapest way to find out what a fix is worth — it ends with a priced list of what to do, which you are free to take elsewhere.
A one-off pipeline, a single migration or a review of one account are all normal. Small first engagements are usually how longer ones start.
I do. There is no team behind this page and nothing is subcontracted — the person who scopes it is the person who builds it and the person you email afterwards.
Six demo applications are online with their source public, and the flagship client work is described by capability where the client is confidential. All of it is on the projects page.
Say what is wrong, or what you need built. A paragraph is enough to start with — I read every enquiry myself and reply from nasvih.va@gmail.com.