Cloud architecture on Azure, Google Cloud and AWS
Choose the right cloud, or make the one you already have work. A clean foundation, designed and built by a working cloud network architect, and written as code so it can be rebuilt on demand.
- Price
- Fixed-fee, quoted after a free call.
- Typical timeline
- 2 to 6 weeks
Sound familiar?
- Someone set up our cloud account years ago and nobody knows what is in it.
- The cloud bill keeps growing and we cannot tell why.
- We need to connect the office to the cloud securely.
- Azure, Google Cloud or AWS? We do not know which one fits.
What is included
- A platform recommendation when you are starting out: Azure, Google Cloud or AWS, based on your applications, your productivity suite and your budget.
- A landing zone: accounts, subscriptions or projects, resource organization, naming and tagging that make sense a year from now.
- Cloud networking: virtual networks, private endpoints, secure connections to your office and no services exposed by accident.
- Identity and role-based access tied to the Google Workspace or Microsoft 365 accounts your staff already use.
- Security baselines, logging and policy guardrails that stop risky configurations before they happen.
- Cost guardrails: budgets, alerts and right-sized resources.
- Compute, containers, data and analytics where they fit, such as BigQuery and Looker on Google Cloud, chosen to match the job, not the trend.
- Everything defined as infrastructure as code, kept in a repository you own.
What you receive at the end
- Infrastructure as code for the whole environment, in your own repository.
- An architecture diagram and a written runbook.
- A walkthrough with your team or provider so they can run it.
Who it suits
- Businesses already on Azure, Google Cloud or AWS that want it cleaned up and secured.
- Teams moving servers or applications into the cloud for the first time.
- Organizations that need a secure link between the office and the cloud.
Where this work happens
Fully remote. Cloud platforms are built and run from a browser and a repository, so location does not matter; Carson City and Reno clients can still have the architecture walkthrough across a table.
Related services
Most clients start with the $1,500 IT and security assessment, so the scope is grounded in facts. This project pairs well with Cloud and infrastructure migration and GitHub, DevOps and automation.
Cloud architecture: common questions
Azure, Google Cloud or AWS: which should we use?
Usually the one that fits what you already run: Azure for Microsoft 365 businesses, Google Cloud for Google Workspace businesses, AWS when your software vendor or developers already live there. The recommendation comes with the reasoning and the monthly cost, not a favorite.
Why infrastructure as code for a small business?
Because it documents itself. Every setting lives in a file you own, changes are reviewed before they happen, and the environment can be rebuilt or audited at any time.
Do we need containers or a data platform?
Most small businesses do not, and you will be told so. Every cloud has a service for almost everything; the job is picking the few you need and leaving the rest alone.
Will this lower our cloud bill?
Usually. Unused and oversized resources are the most common finding, and cost guardrails keep it from creeping back.
Talk it through first
Every cloud architecture project is fixed-fee, quoted after a free call. Many clients start with the $1,500 IT assessment so the scope is grounded in facts.