Alternatives to Cloud 66 logo

Alternatives to Cloud 66

Heroku, Codeship, Buddy, AWS CodePipeline, and DeployBot are the most popular alternatives and competitors to Cloud 66.
26
21
+ 1
83

What is Cloud 66 and what are its top alternatives?

Cloud 66 makes Ops easy for developers. It is a single tool built for developers to build, configure and maintain servers and Docker containers on your own servers.
Cloud 66 is a tool in the Continuous Deployment category of a tech stack.

Cloud 66 alternatives & related posts

Heroku logo

Heroku

7.7K
5.4K
3.1K
7.7K
5.4K
+ 1
3.1K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
Heroku logo
Heroku
VS
Cloud 66 logo
Cloud 66

related Heroku posts

Tim Nolet
Tim Nolet
Founder, Engineer & Dishwasher at Checkly · | 17 upvotes · 161.6K views
atChecklyHQChecklyHQ
vuex
vuex
Knex.js
Knex.js
PostgreSQL
PostgreSQL
Amazon S3
Amazon S3
AWS Lambda
AWS Lambda
Vue.js
Vue.js
hapi
hapi
Node.js
Node.js
GitHub
GitHub
Docker
Docker
Heroku
Heroku

Heroku Docker GitHub Node.js hapi Vue.js AWS Lambda Amazon S3 PostgreSQL Knex.js Checkly is a fairly young company and we're still working hard to find the correct mix of product features, price and audience.

We are focussed on tech B2B, but I always wanted to serve solo developers too. So I decided to make a $7 plan.

Why $7? Simply put, it seems to be a sweet spot for tech companies: Heroku, Docker, Github, Appoptics (Librato) all offer $7 plans. They must have done a ton of research into this, so why not piggy back that and try it out.

Enough biz talk, onto tech. The challenges were:

  • Slice of a portion of the functionality so a $7 plan is still profitable. We call this the "plan limits"
  • Update API and back end services to handle and enforce plan limits.
  • Update the UI to kindly state plan limits are in effect on some part of the UI.
  • Update the pricing page to reflect all changes.
  • Keep the actual processing backend, storage and API's as untouched as possible.

In essence, we went from strictly volume based pricing to value based pricing. Here come the technical steps & decisions we made to get there.

  1. We updated our PostgreSQL schema so plans now have an array of "features". These are string constants that represent feature toggles.
  2. The Vue.js frontend reads these from the vuex store on login.
  3. Based on these values, the UI has simple v-if statements to either just show the feature or show a friendly "please upgrade" button.
  4. The hapi API has a hook on each relevant API endpoint that checks whether a user's plan has the feature enabled, or not.

Side note: We offer 10 SMS messages per month on the developer plan. However, we were not actually counting how many people were sending. We had to update our alerting daemon (that runs on Heroku and triggers SMS messages via AWS SNS) to actually bump a counter.

What we build is basically feature-toggling based on plan features. It is very extensible for future additions. Our scheduling and storage backend that actually runs users' monitoring requests (AWS Lambda) and stores the results (S3 and Postgres) has no knowledge of all of this and remained unchanged.

Hope this helps anyone building out their SaaS and is in a similar situation.

See more
Ganesa Vijayakumar
Ganesa Vijayakumar
Full Stack Coder | Module Lead · | 15 upvotes · 297K views
SonarQube
SonarQube
Codacy
Codacy
Docker
Docker
Git
Git
Apache Maven
Apache Maven
Amazon EC2 Container Service
Amazon EC2 Container Service
Microsoft Azure
Microsoft Azure
Amazon Route 53
Amazon Route 53
Elasticsearch
Elasticsearch
Solr
Solr
Amazon RDS
Amazon RDS
Amazon S3
Amazon S3
Heroku
Heroku
Hibernate
Hibernate
MySQL
MySQL
Node.js
Node.js
Java
Java
Bootstrap
Bootstrap
jQuery Mobile
jQuery Mobile
jQuery UI
jQuery UI
jQuery
jQuery
JavaScript
JavaScript
React Native
React Native
React Router
React Router
React
React

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more

related Codeship posts

Sebastian Dellwig
Sebastian Dellwig
Tech Lead at Porsche Digital GmbH · | 6 upvotes · 16.9K views
Codeship
Codeship
CircleCI
CircleCI
GitLab CI
GitLab CI

We are using GitLab CI and were very happy with it. The integration of all tools like CI/CD, tickets, etc makes it very easy to stay on top of things. But be aware, Gitlab currently does not have iOS build support. So if you want to exchange that for CircleCI / Codeship to have to invest some effort. We are using a managed Mac OS device and installed the Gitlab runner there, to have iOS builds.

See more
GitHub
GitHub
Slack
Slack
Semaphore
Semaphore
Codeship
Codeship

When it comes to continuous Integration services, the choice is hard. There are several solutions available and it looks like the dev scene is very split. We've read and reviewed several solutions and we ended up making the choice between Codeship and Semaphore . Although Semaphore is used by slightly more developers, we've experienced a faster and easy flow using Codeship. Both do integrate Slack and GitHub very well, so this is not a point to set them apart. Both have a complex pricing system that is not that easy to calculate and predict. However, out in the wild, we found Codeship to have a better price point at heavy use.

See more

related Buddy posts

Epistol
Epistol
PHP
PHP
Bulma
Bulma
Asana
Asana
Stripe
Stripe
Let's Encrypt
Let's Encrypt
CloudFlare
CloudFlare
Deployer
Deployer
Git
Git
GitHub
GitHub
Ubuntu
Ubuntu
nginx
nginx
Buddy
Buddy
Webpack
Webpack
Vue.js
Vue.js
JavaScript
JavaScript
HTML5
HTML5
Sass
Sass
Google Analytics
Google Analytics
PhpStorm
PhpStorm
Laravel
Laravel
#CDG
CDG

I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.

Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.

As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.

To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .

CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.

Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.

See more
AWS CodePipeline logo

AWS CodePipeline

135
76
8
135
76
+ 1
8
Continuous delivery service for fast and reliable application updates
AWS CodePipeline logo
AWS CodePipeline
VS
Cloud 66 logo
Cloud 66

related AWS CodePipeline posts

Oliver Burn
Oliver Burn
Architect at Atlassian · | 12 upvotes · 82.9K views
atAtlassianAtlassian
Azure Pipelines
Azure Pipelines
jFrog
jFrog
Octopus Deploy
Octopus Deploy
AWS CodePipeline
AWS CodePipeline
CircleCI
CircleCI
Bitbucket
Bitbucket
Jira
Jira

We recently added new APIs to Jira to associate information about Builds and Deployments to Jira issues.

The new APIs were developed using a spec-first API approach for speed and sanity. The details of this approach are described in this blog post, and we relied on using Swagger and associated tools like Swagger UI.

A new service was created for managing the data. It provides a REST API for external use, and an internal API based on GraphQL. The service is built using Kotlin for increased developer productivity and happiness, and the Spring-Boot framework. PostgreSQL was chosen for the persistence layer, as we have non-trivial requirements that cannot be easily implemented on top of a key-value store.

The front-end has been built using React and querying the back-end service using an internal GraphQL API. We have plans of providing a public GraphQL API in the future.

New Jira Integrations: Bitbucket CircleCI AWS CodePipeline Octopus Deploy jFrog Azure Pipelines

See more
Khauth György
Khauth György
CTO at SalesAutopilot Kft. · | 11 upvotes · 79.6K views
atSalesAutopilot Kft.SalesAutopilot Kft.
AWS CodePipeline
AWS CodePipeline
Jenkins
Jenkins
Docker
Docker
vuex
vuex
Vuetify
Vuetify
Vue.js
Vue.js
jQuery UI
jQuery UI
Redis
Redis
MongoDB
MongoDB
MySQL
MySQL
Amazon Route 53
Amazon Route 53
Amazon CloudFront
Amazon CloudFront
Amazon SNS
Amazon SNS
Amazon CloudWatch
Amazon CloudWatch
GitHub
GitHub

I'm the CTO of a marketing automation SaaS. Because of the continuously increasing load we moved to the AWSCloud. We are using more and more features of AWS: Amazon CloudWatch, Amazon SNS, Amazon CloudFront, Amazon Route 53 and so on.

Our main Database is MySQL but for the hundreds of GB document data we use MongoDB more and more. We started to use Redis for cache and other time sensitive operations.

On the front-end we use jQuery UI + Smarty but now we refactor our app to use Vue.js with Vuetify. Because our app is relatively complex we need to use vuex as well.

On the development side we use GitHub as our main repo, Docker for local and server environment and Jenkins and AWS CodePipeline for Continuous Integration.

See more
DeployBot logo

DeployBot

79
52
76
79
52
+ 1
76
Instantly deploy from Github, Bitbucket, or Gitlab without complex scripts, commands or configs.
DeployBot logo
DeployBot
VS
Cloud 66 logo
Cloud 66
Spinnaker logo

Spinnaker

52
46
1
52
46
+ 1
1
Multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence
Spinnaker logo
Spinnaker
VS
Cloud 66 logo
Cloud 66

related Spinnaker posts

John Kodumal
John Kodumal
CTO at LaunchDarkly · | 3 upvotes · 27.8K views
atLaunchDarklyLaunchDarkly
Armory
Armory
Packer
Packer
Terraform
Terraform
Spinnaker
Spinnaker
Ansible
Ansible

LaunchDarkly is almost a five year old company, and our methodology for deploying was state of the art... for 2014. We recently undertook a project to modernize the way we #deploy our software, moving from Ansible-based deploy scripts that executed on our local machines, to using Spinnaker (along with Terraform and Packer) as the basis of our deployment system. We've been using Armory's enterprise Spinnaker offering to make this project a reality.

See more
Google Cloud Build logo

Google Cloud Build

44
15
0
44
15
+ 1
0
Continuously build, test, and deploy.
    Be the first to leave a pro
    Google Cloud Build logo
    Google Cloud Build
    VS
    Cloud 66 logo
    Cloud 66

    related Google Cloud Build posts

    Emanuel Evans
    Emanuel Evans
    Senior Architect at Rainforest QA · | 12 upvotes · 100.8K views
    atRainforest QARainforest QA
    Terraform
    Terraform
    Helm
    Helm
    Google Cloud Build
    Google Cloud Build
    CircleCI
    CircleCI
    Redis
    Redis
    Google Cloud Memorystore
    Google Cloud Memorystore
    PostgreSQL
    PostgreSQL
    Google Cloud SQL for PostgreSQL
    Google Cloud SQL for PostgreSQL
    Google Kubernetes Engine
    Google Kubernetes Engine
    Kubernetes
    Kubernetes
    Heroku
    Heroku

    We recently moved our main applications from Heroku to Kubernetes . The 3 main driving factors behind the switch were scalability (database size limits), security (the inability to set up PostgreSQL instances in private networks), and costs (GCP is cheaper for raw computing resources).

    We prefer using managed services, so we are using Google Kubernetes Engine with Google Cloud SQL for PostgreSQL for our PostgreSQL databases and Google Cloud Memorystore for Redis . For our CI/CD pipeline, we are using CircleCI and Google Cloud Build to deploy applications managed with Helm . The new infrastructure is managed with Terraform .

    Read the blog post to go more in depth.

    See more
    Travis CI
    Travis CI
    CircleCI
    CircleCI
    Google Cloud Build
    Google Cloud Build

    I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

    I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

    One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

    Feel free to checkout an example: Cloudbuild Example

    See more
    Deployer logo

    Deployer

    41
    43
    21
    41
    43
    + 1
    21
    Deployment Tool for PHP
    Deployer logo
    Deployer
    VS
    Cloud 66 logo
    Cloud 66

    related Deployer posts

    Epistol
    Epistol
    PHP
    PHP
    Bulma
    Bulma
    Asana
    Asana
    Stripe
    Stripe
    Let's Encrypt
    Let's Encrypt
    CloudFlare
    CloudFlare
    Deployer
    Deployer
    Git
    Git
    GitHub
    GitHub
    Ubuntu
    Ubuntu
    nginx
    nginx
    Buddy
    Buddy
    Webpack
    Webpack
    Vue.js
    Vue.js
    JavaScript
    JavaScript
    HTML5
    HTML5
    Sass
    Sass
    Google Analytics
    Google Analytics
    PhpStorm
    PhpStorm
    Laravel
    Laravel
    #CDG
    CDG

    I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.

    Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.

    As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.

    To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .

    CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.

    Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.

    See more
    DeployHQ logo

    DeployHQ

    9
    6
    0
    9
    6
    + 1
    0
    Deploy your websites or apps directly from your repository to servers or the cloud
      Be the first to leave a pro
      DeployHQ logo
      DeployHQ
      VS
      Cloud 66 logo
      Cloud 66
      Continuous Delivery Service logo

      Continuous Delivery Service

      8
      24
      0
      8
      24
      + 1
      0
      Enterprise-Grade Continuous Delivery & DevOps Automation Open Source Platform (by OVH)
        Be the first to leave a pro
        Continuous Delivery Service logo
        Continuous Delivery Service
        VS
        Cloud 66 logo
        Cloud 66
        Weaveworks Flux logo

        Weaveworks Flux

        4
        0
        0
        4
        0
        + 1
        0
        The operator that makes GitOps happen in your cluster
          Be the first to leave a pro
          Weaveworks Flux logo
          Weaveworks Flux
          VS
          Cloud 66 logo
          Cloud 66
          Armory logo

          Armory

          4
          8
          0
          4
          8
          + 1
          0
          Make Deployments Boring and Self-Service
            Be the first to leave a pro
            Armory logo
            Armory
            VS
            Cloud 66 logo
            Cloud 66

            related Armory posts

            John Kodumal
            John Kodumal
            CTO at LaunchDarkly · | 3 upvotes · 27.8K views
            atLaunchDarklyLaunchDarkly
            Armory
            Armory
            Packer
            Packer
            Terraform
            Terraform
            Spinnaker
            Spinnaker
            Ansible
            Ansible

            LaunchDarkly is almost a five year old company, and our methodology for deploying was state of the art... for 2014. We recently undertook a project to modernize the way we #deploy our software, moving from Ansible-based deploy scripts that executed on our local machines, to using Spinnaker (along with Terraform and Packer) as the basis of our deployment system. We've been using Armory's enterprise Spinnaker offering to make this project a reality.

            See more
            Gaia logo

            Gaia

            3
            16
            0
            3
            16
            + 1
            0
            Build pipelines in any programming language
              Be the first to leave a pro
              Gaia logo
              Gaia
              VS
              Cloud 66 logo
              Cloud 66
              Teletraan logo

              Teletraan

              2
              11
              0
              2
              11
              + 1
              0
              Pinterest's deploy system
                Be the first to leave a pro
                Teletraan logo
                Teletraan
                VS
                Cloud 66 logo
                Cloud 66
                DeployPlace logo

                DeployPlace

                1
                2
                0
                1
                2
                + 1
                0
                Automate deployments with your custom-ready CI even for very complex apps, to your servers or cloud
                  Be the first to leave a pro
                  DeployPlace logo
                  DeployPlace
                  VS
                  Cloud 66 logo
                  Cloud 66