We charge a fraction of what it costs to do it in-house and deliver it in half the time or faster. Check out our calculator just to see how much it can cost to build your own cloud infrastructure. Make sure you review some of the risks of doing it yourself.

We practice "agile" development. We charge a flat fee per sprint, but allow for scope changes (which are billed separately) at customer request. A typical engagement consists on 6-8 sprints ranging in 1-2 weeks in duration. 

We're a motley crew of software engineers who all found their calling in DevOps/SRE arena. We have a mix of complementary skill sets that help us work with a diverse range of companies. Everyone on our team has years of software development experience. We believe this is essential because developers are fundamentally against doing things over and over by hand.

1. Based Open Source. Everything we do is available for free today on our GitHub. This is our proof we know what we're talking about. "What You See is What You Get" - no other company can provide such a comprehensive solution based on Open Source.
2. Free Weekly Office Hours Our commitment to help others is in our DNA. We want to make sure you get the maximum value out of your investment.
3. Massive Community Adoption ensures our projects get regular updates and bug fixes.

"Rising tide floats all boats"

After working with so many startups over the years, it became very apparent that a lot of what tech companies need is repeatable. Also, figuring out how to get all the Open Source components working together was always a big challenge.

As consultants, we needed to find a way to consistently deliver the results our customers expect. Starting from scratch is simply not feasible, if we want to scale our business.

Therfore we decided to use an Open Source business model whereby all reusable pieces of infrastructure code are released on our GitHub under the permissive Apache 2 software license. This ensures that we can continue to iterate on everything we develop for our customers. Everyone wins.

Our typical engagement model begins with a complete platform rollout. This includes roughly 6-8 sprints, each 1-2 week in duration. During this time we setup all AWS Accounts with IAM federation, Cloud Trail audit logs, a comprehensive release engineering process, total observability with our Site Reliability Engineering (SRE) sprint, Remote Access Management (Teleport and KeyCloak), GitOps Operations by Pull Request.

The first engagement takes roughly 3-4 months to complete. These engagements have an extremely well-defined project plans. Ask us and we can show you what that looks like. 

Absolutely not. You can cancel anytime. 

We'll sign a few contracts before we get started:

1. Mutual NDA that describes how we'll govern sensitive information
2. Master Services Agreement that describes the terms for all engagements we'll do down the road
3. Statement of Work that describes at length exactly what you'll receive.

Our standard payment terms are Net 15.

Payment for each Sprint is due before work commences.

As a small business we cannot afford to extend a line of credit to our customers.

We believe in total transparency.

For this reason, you can expect no hidden fees from us.

IMPORTANT: Depending on the features you want implemented, certain third party software subscriptions may be required (SaaS).

We do not include these costs in our contract because they are negotiated between your company and the vendor. Sometimes you may qualify for "startup" pricing.

Examples include:

• AWS
• Datadog
• NewRelic
• Sumologic
• Splunk
• Codefresh
• Teleport
• Kubecost
• Mailgun
• PagerDuty
• Pingdom

It really depends on when a contract begins and who on our team is on the bench. Generally, we like to put (2) engineers on a project so we have cross-training and continuity in the event a member needs to take time off. For our standard engagements, we're more adept at parallelizing the work because the scope of work is quite well understood. For engagements that require R&D or are smaller in scope, we may be limited in parallelizing the work and only have (1) member on the project. Our team is geographically distributed across the continental US as well as Eastern Europe. Throughout the course of a project,  we may move team members around or experience the standard ebb and flow of developers in a high-value market.

That's easy.

1. Book your discovery call: cloudposse.com/booking
2. Watch our training video so we're all on the same page
3. Introduce us with your decision maker so we can get the ball rolling

Your best bet is let us take your team through a quick live demo via Zoom. They will instantly see the value of our DevOps Accelerator. They can spend far less time spinning their wheels trying to get all the open source components working and be able to spend more time on building your product and infrastructure to serve you.

Cloud Posse takes the guesswork out of DevOps.

Start by signing up for a demo today! Then invite your team. 

cloudposse.com/booking

Our experience ensures you reach your goals in record time. Time is money. Salaries are by far the biggest cost for most startups make. Think about how much you would pay to do this in-house and combine that with how long it will take you. During that time, your teams will be blocked or at the very least slowed down. Plus, you don't even have a predictable outcome. You can easily quantify this as your opportunity cost.

Our solution will pay for itself. You get a predictable solution delivered in record time for a fair price. Your engineers will be unblocked sooner and you'll be able to move faster.

Make sure you include all costs associated with your project.

• What is the cost of recruiting your team?
• What is your teams fully-loaded cost? 
• How long will it take to build and train the team?
• Will they stick around long enough to see the project through?
• What happens when everyone goes on holiday or takes a vacation?
• Will you have enough work for them when the project is over?

Our total project costs a predictable. You'll know upfront what to expect and there are no surprises.

We can start as soon as you sign our Statement of Work. Typically we see this process take 2-3 weeks from the first introductory call to the start of our engagement . 

Here's our checklist we'll need to complete before we can start.

1. Execute Statement of Work
2. Execute Master Services Agreement & Mutual NDA
3. Receive Payment for the First Sprint

We can kick off the initial introductory call immediately, so please make sure that you schedule it today. 

After talking with you and assessing if we're a proper fit, we'll put together a detailed "Statements of Work" in less than one business day which lays out our entire plan for the project.

The short answer is "no". As a DevOps Accelerator one of mission is to empower our customers to take over everything once we’re done. However, we don't expect this to happen overnight, so we'll stick around as long as you need our help. 

We provide entirely optional ongoing support.

By in large, most of our customers take over the day to day management of their infrastructure.

We're here though to help out anywhere you need it.

We do not provide 24x7 "on call" (aka PagerDuty) support.

1. Slack. You will have direct access to the team via a shared Slack channel between our respective teams.
2. Zoom. We'll have weekly scheduled cadence calls via Zoom to review the current progress, blockers and give product demos in your environment. These calls can be recorded and shared with your team.
3. Google Drive. We also recommend creating a shared Team Drive folder via Google Docs for sharing of relevant design docs, agendas or other materials.
4. Trello. We manage the project via a Trello Team created specifically for each engagement. We invite your team and our team to this team and create (1) board per sprint. This allows us to standardize our process while providing transparency along the way.
5. Office Hours. Most engagements include a “Documentation & Training” sprint, we arrange a weekly “Office Hours” via Zoom (recorded) to answer any questions your team may have as they begin to kick the tires.

We’ve designed our own flavor of the “agile” development process which enables us to better parallelize work to achieve aggressive timelines.

The traditional agile sprint methodology doesn't work for the velocity move at. This is a situation that’s somewhat unique to a consultancy like ours, which implements repeatable solutions. Our team members are coming on and off of projects, or get blocked on tasks they are working on for other customers. When this happens, using our methodology they can easily pick up slack in other areas. In certain situations, we may tap members with specific specializations to work on a sprint.

We define sprints in terms of effort (man hours) of either 1 or 2 weeks (40 - 80 hours). Sprints do not necessarily correspond to a calendar week, but they do have a calendar due date. In a given week, one sprint is the priority which is the one with the nearest delivery date.

As part of our process, when we write a Statement of Work, we decide upfront the deliverables for a given sprint. When a sprint grows beyond what we think we can achieve in the fixed amount of time, we split it off into a new sprint.

Every sprint is thematic; that is, it speaks to some greater, overarching goal or milestone with a clear set of deliverables. At any given time, we may have multiple people working on different parts of a project across multiple different sprints. However, since we sometimes have extra resources on hand, we can front load work. This is especially valuable on sprints which may require more research or involve more interrupts.

We log detailed time entries against our time accounting software (Harvest) which has a project allocated for each Sprint that corresponds to a Kanban board. This ensures that we have proper time accounting and everything lines up business wise.

We'll deliver the end-to-end solution you've seen in all of our demos. It will be preconfigured for your environments under your AWS accounts. We'll create new GitHub repos that will contain all the infrastructure code you need.

When we're done, we'll show you the ropes and how to operate it. In the long run, you'll be responsible for operating it but we'll stick around for as long as you need our help.

We offer all of our customers on going support for as long as they need it. Choose what's right for you.

• We provide free weekly support via our "Office Hours" webinars every Wednesday at 11:30am PST. These calls last one hour and we'll answer as many of your questions as we can.
• We also provide optional support retainers which include a fixed block of hours that go towards maintenance and support. You'll have direct access to our team via a shared Slack channel in addition to the ability to schedule one-on-one calls via Zoom.

Your best bet is to schedule a discovery call with us so we can go over your specific concerns. Assuming your software runs on Linux and that you're able to make any necessary code changes to ensure your applications are "12 factor" compliant, there's a very high likelihood we'll be able to help you out.

We have a very specific mission, which means we may not be a good fit for all companies.

1. Companies who are too small (1-2 engineers) may struggle with the upkeep of managing their own infrastructure.
2. Companies who do not commit any in-house resources to learning the new software stack will have a tough time (you own it after all!)
3. Companies who prefer to use different tools than we prescribe may run into integration challenges (we recommend what we know works)

If any of these sound familiar, please discuss with us before proceeding.

Here are some additional resources you can review:

• Our GitHub is where we publish over 140 terraform modules we've written and open sourced under the Apache 2 software license. Our repos see over 11K unique visitors every single day and have over 5000 stars. We receive dozens of Pull Requests every week.
• Our Reviews are glowing both from our customers and from our community.
• Our Community will tell you how much we've helped them. You can scan through all of our archives to see what they say.
• Our YouTube Channel showcases many of our presentations and webinars
• Our Service Catalog is what lets us rapidly deploy the applications you see in our demos
• Our Work is Cited in academic papers by Caltech.

Of course! We can't wait to show you what it can do.

Book your appointment today.

Just go to: cloudposse.com/booking

What’s it costing your business if you wait?

The longer you wait, the more time & effort you'll waste on maintenance rather than innovation. The more tech debt you'll amass. The more opportunities you'll miss.

Your developers will be less productive, which means you'll be paying more while getting less done in return.

The sooner you streamline your operations the faster you will move:

1. Reduce your opportunity cost and capitalize on the investment sooner
2. Release more features to customers faster
3. Control operating costs to do more for less

Not to mention, your developers will love you for making their lives easier. The last thing developers want is to do things by hand.