Friends of this blog know that I am a big fan of building internal tools, or as we call them, "tools that help scale people". As the name suggests, internal tools are used, well, internally and as such usually will require their access to be restricted to the company's staff and network. In the past, I've written about how to use Tailscale for authentication of internal tools using HTTP. In this post, I will show you how to use Tailscale for gRPC authentication in Golang.

Today we have rolled out a change in the way you can configure each deployment of your application. Normally you deploy your apps, using the Deploy button on the top right corner of your application page. This will deploy your application based on the "default" Deployment Profile. You can also customize your deployment, using the "Deploy with Options" item on the deploy menu. With today's rollout, we've made improvements to this flow.

This blog post aims to dissect the various deployment options available for Rails applications in 2024, emphasizing the choice between native and containerized approaches. It dives into the advantages and drawbacks of each method and explores the hosting options available for each. Let’s dive right in!

Amazon Simple Email Service (SES) is a cost-effective email service provided by AWS. It is by far the cheapest option available out there. Comparing the cost of sending emails with SES and other services like SendGrid or Mailchimp, it can be 100x cheaper. However there is a catch. Using SES directly, you will not get some of the features you might need to control the bounce rate of your emails.

We’ve been busy building a few features that are going to be very useful for teams at larger companies using Cloud 66: Automatic User Provisioning and SAML SSO.

JWT is a popular way for authentication and authorization, especially for service to service communications. When it comes to internal tools, distribution and renewal of JWT can become a challenge. Our internal support systems use JWT to authenticate and authorize access and they are written in a few different languages and run on different hosting options.

Google Identity-Aware Proxy (IAP) is a Google Cloud service that provides authentication for web applications. This service simplifies the process of building web applications authenticated with Google, eliminating the need to handle user-related concerns within your application code. This is especially valuable for internal applications within organizations that already utilize GSuite. It is straightforward to use, particularly when operating on Google Cloud.

Ok there is a lot to unpack, so let’s jump right in.

Today I am thrilled to introduce our Intelligent Deployment Analysis feature, designed to significantly improve your troubleshooting process. Picture this: you're stuck, scratching your head over what went wrong with your deployment - was it the Node.js asset compiler or a missing package in your Dockerfile?

To celebrate a 3-year integration anniversary between Cloud 66 and Vultr we’re showcasing some of the changes and improvements that we have implemented in both of our platforms. To show how well our platforms work together, we’re taking a Rails 7 application sample and walking you through how to containerize and deploy that application on Vultr with Cloud 66.