AWS migration, re-architecture & deployment
The AWS and DevOps team you haven't hired yet.
You have developers. You don't have a DevOps engineer. We migrate your systems to AWS, re-architect what needs it, set up deployment your whole team can run, and hand over a documented platform, at a fixed price agreed in writing.
Readiness assessment $4,900, delivered in 15 business days · Migrations from $14,900 · No subscriptions
Sound familiar?
The pattern we see at companies with 3 to 15 engineers and nobody whose job is the cloud.
Developers run the cloud between features
Deploys happen from one engineer's laptop, infrastructure changes are made by hand in the console, and nobody owns the AWS bill. Product work slows down every time something breaks.
You have outgrown Heroku, Render or a single server
The platform that got you to your first customers is now the most expensive and least flexible part of your stack, but moving to AWS looks like a three-month project nobody has time for.
The first enterprise customer sent a security questionnaire
Encryption at rest, backups, access control, incident response. The honest answer today is “we think so”, and the deal is waiting on a better one.
Hiring a DevOps engineer is slow and starts from zero
A first platform hire takes months to find and needs a roadmap to work from. Until then, the same three developers carry infrastructure, on-call and delivery at once.
What we take off your developers
Senior AWS and security engineers doing the platform work, so your team ships product.
AWS migration
From Heroku, Render, DigitalOcean, a VPS or an on-premise server to a properly structured AWS account: networking, identity, databases, storage and a cut-over plan with rollback.
Re-architecture
Split what needs splitting and leave the rest alone. Managed databases, queues, containers or serverless where they pay off, sized for the traffic you actually have.
Deployment and CI/CD
Infrastructure as code, automated tests and pipelines, staging and production environments, and releases any developer on the team can run without fear.
Security, backups and cost
Least-privilege access, encryption, backup and restore that has been tested, monitoring and alerting, and a bill you can explain. The evidence procurement teams ask for, ready before they ask.
How it works
Start small, stop whenever you want. Each step stands on its own and produces something you keep.
30 minutes, free
1. Readiness call
A free 30-minute call about your stack, your team and what is slowing you down. If we are not the right fit, we say so and point you somewhere useful.
15 business days
2. Migration readiness assessment
The fixed-price Cloud Foundations assessment: a review of your current setup, a ranked risk register, a target AWS architecture and a sequenced migration roadmap with effort estimates. Yours to keep, whoever does the work.
4–8 weeks
3. Migration, re-architecture and deployment
A Build & Launch engagement against a statement of work with acceptance criteria. Infrastructure as code, CI/CD, documentation and a knowledge-transfer session land with the work, not after it.
Fixed term, in writing
4. Operating cover while you hire
A fixed-term managed delivery window with agreed support hours and response targets, so the people who built the platform keep it running until your own hire is in place. Never an auto-renewing subscription.
Full scope, exclusions and cancellation terms for each plan are on Plans & pricing.
What you are left with
A platform your developers can run and your future DevOps hire can pick up on day one. Nothing depends on keeping us around.
- Infrastructure defined as code in your own repository
- Architecture diagram and account inventory a new hire can read on day one
- Runbooks for deploys, rollbacks, backups and the incidents most likely for your workload
- CI/CD pipelines with tests, staging and production promotion
- Access, encryption and backup evidence for security questionnaires
- A knowledge-transfer session recorded for your team
Hire a DevOps engineer, or borrow one?
A first platform hire is the right call eventually. Until then, the choice is between a months-long search while developers cover infrastructure, or a scoped engagement that leaves a documented platform behind, one your eventual hire inherits instead of rebuilds.
We are not trying to replace that hire. We are trying to make sure they start with a roadmap, working pipelines and runbooks, and that your team is not blocked while you look.
Why teams pick this route
- Price and scope in writing before anything starts, never hourly drift
- Work done in your AWS accounts and repositories, so nothing is locked in
- Security and compliance evidence produced as part of the build, not bolted on
- A founder reads every message and replies within one business day
- Plans are one-time engagements; ongoing cover is fixed-term and never auto-renews
Who does the work
Farqad Cloud was founded by a small group of engineers who spent the better part of two decades building, securing, and reviewing systems for other organizations before starting their own.
We are certified practitioners, not generalists: our credentials span AWS and Google Cloud, SANS/GIAC, and Offensive Security, covering cloud architecture, defensive security, and hands-on offensive testing. That mix means we can design a system, break it, and then fix what we found.
Our work has taken us through fintech and payment platforms, cloud migrations and greenfield builds, and regulated environments where compliance is not optional. We have delivered against GDPR, HIPAA, and ISO 27001 requirements, as well as local regulatory frameworks in Egypt, the Gulf, Europe, and the United States — so when your auditor or your enterprise customer asks a question, we already know what evidence they expect.
Practitioner credentials
- Cloud architecture and operations: AWS, Google Cloud
- Defensive security: SANS / GIAC
- Offensive testing: Offensive Security
Certificates held by individual engineers, not a company certification.
Delivered in
- Fintech and payment platforms
- Cloud migrations and greenfield builds
- Regulated environments
Against requirements from
- GDPR
- HIPAA
- ISO 27001 requirements
- Local frameworks in Egypt, the Gulf, Europe, and the United States
Questions teams ask before the first call
- We have no DevOps engineer. Who runs the platform after you leave?
- Your developers, from the runbooks and pipelines we hand over, or the DevOps engineer you hire later, who starts with a documented platform instead of archaeology. If you want cover in between, a fixed-term managed delivery window keeps us involved for an agreed period. It is written into the statement of work and never auto-renews.
- Do we have to buy the assessment before a migration?
- No. If the scope is already clear, we quote a Build & Launch engagement directly. The assessment exists for teams that want an independent plan and a price before committing budget, and its roadmap becomes the scoping input for the build, so nothing is wasted.
- How much does an AWS migration cost?
- The readiness assessment is a fixed $4,900. Migration and re-architecture engagements start at $14,900 and are quoted after the assessment or a scoping call, with the price and acceptance criteria written into a statement of work before work begins. Your own AWS usage is billed to you by AWS.
- Are you AWS certified?
- Our engineers hold individual practitioner credentials from AWS and Google Cloud, and security credentials from SANS/GIAC and Offensive Security. These are certificates held by people on the team, not a company certification or a vendor partnership, and we do not claim badges we have not earned.
- Can you work in our timezone?
- Default support hours are Monday–Friday, 09:00–17:00 (UTC). Overlapping coverage for other timezones is arranged in the statement of work for build and managed delivery engagements.
- Who owns the infrastructure code and documentation?
- Everything is built in your accounts and your repositories. Upon full payment you receive a licence to use the deliverables for your business, or an ownership transfer when the statement of work says so. Your pre-existing materials always remain yours.
Tell us what you're running today
Your stack, your team size, and what is slowing you down. A founder reads every message and replies within one business day with next steps, or an honest “not us”.