Aptible has a new look. But more importantly, we want to talk about the future of platform as a service, and how we intend to rapidly expand the value our platform delivers to you. Also, it’s the Aptible platform’s birthday!

You might’ve noticed a few changes on aptible.com, in our docs, and in our product. Our visual design, how we talk about ourselves, our pricing page, and the product dashboard. What’s going on you ask?

Aptible has been fortunate to experience steady growth in our user base for the last 10 years, thanks primarily to the resilience and growth of our customers. Today marks the Aptible platform’s 9th official birthday. It also marks the beginning of the future for Aptible.

We’re proud of how far we’ve come since the platform launched on March 21, 2014. But there’s so much more ground to cover if we’re going to achieve our vision of making it possible for any developer and company to launch and scale products without building and managing infrastructure.

Over the years we’ve gotten countless suggestions and ideas on how to improve our PaaS. The most useful source of feedback has been the hundreds of calls we’ve had with existing customers, and the many we’ve had with prospective customers as well. We intend to continue these discovery processes and, in fact, we intend to accelerate our pace of learning further.

Today’s changes are just a step in that direction. While we plan to rapidly expand the value our product provides to customers, and to iterate quickly, what we are “soft launching” today is just the first in a long line of changes we anticipate making. All with the same end goal in mind: continually improving how we eliminate the pains of building and managing infrastructure for companies like yours.

Upcoming changes that we’re particularly excited about are:

But that’s just three changes. What’s guiding our focus moving forward?

While we’ve long delivered different user interfaces for our PaaS–CLI, Terraform, Dashboard–the developer experience, especially of our Dashboard, has become a bit dated. It certainly wasn’t the “magical” experience developers expect, or the one we want to deliver to make good on our promise to eliminate the pains of building and managing infrastructure.

We’re just at the beginning of this journey to deliver a magical developer experience. Our team is completely reimagining how developers use Aptible, making it more like this: 

At the same time, we continue to tackle the really hard scaling problems we’ve worked with hundreds of fast growing companies to solve. Problems such as: optimizing resource costs via autoscaling, right-sizing, and instance class tuning, deploying complex architectures just as easily as monolithic web apps, and finding and fixing performance bottlenecks in distributed systems.

Building for all startups–and every company

Hundreds of digital health companies have used Aptible to go from 2 developers in a garage to unicorn status, successful acquisition, and even IPO. But few outside of digital health know of Aptible. 

Aptible has great security and compliance benefits that are, in truth, industry agnostic. While we’ll continue to ensure we’re the best PaaS for digital health startups, we know our PaaS can be useful to every startup, regardless of industry focus.

Thinking longer term, the reason Aptible exists is to enable every developer to focus on ideas, not infrastructure. We want to empower all developers to build valuable products for their customers, without dealing with the pain of building or managing infrastructure. This goes for all developers, from those working at early stage startups to those on enterprise product teams.

We believe that “No Infrastructure” is the future of software development. You’ll hear us talk about our “No Infrastructure” vision of the future more and more as we go forward. 

While it may not feel as substantial as our plans to deliver magical developer experiences and tackling the scaling problems companies face, we’ve also updated our brand look and feel. We wanted a new, bright look that complements our optimistic outlook and commitment to our No Infrastructure vision. 

Of course, we love the Aptible arrow logo and didn’t want to replace it. So we turned to our friends at 

, who helped us with our previous successful visual redesign. We went through several (SEVERAL) versions while we collaboratively iterated towards the look and feel that most resonated with our team and the value we want to bring to our customers. 

We hope you agree that this is a much needed improvement to our brand without straying too far from what worked well.

Aptible pricing has stayed consistent for about a decade. We’re investing in ways to help companies manage costs on Aptible. The first two changes, while smaller, are a strong platform we can use to continue to improve how we help customers manage costs. Initially, we are releasing:

With Limits, companies can be sure to limit their infrastructure costs without running the risk of downtime. If you select a Limit (today, you’d select a Limit by picking a Plan), Aptible will ensure you don’t provision resources that would raise you above the max limits–and the max invoice–you’ve chosen.

Plans are the primary vehicle we are (currently) using to experiment with Limits. The point is to make it easier for companies to “choose” where they want their infrastructure spend to be based on the size, scale, and maturity of their project. 

For now, all existing Aptible customers will be grandfathered on their current pricing plan, and will not have Limits enforced. Going forward, based on your feedback, we may make Limits accessible beyond the first set of Plans we’ve implemented, making them available across the customer base. Beyond that, we anticipate continuously releasing cost optimization tools to help you control your Aptible invoice.

We’re still the same Aptible that hundreds of companies and thousands of developers have trusted to run their infrastructure for the past decade. We’re just making some changes, seeking to accelerate investment in our PaaS, ensuring we are continuously improving on how we deliver our “No Infrastructure” vision, and being the best PaaS for both starting and scaling a company on, without the pain of managing infrastructure.

Don’t hesitate to reach out to any of us or your account manager if you have any questions, suggestions, or requests. We’d love to hear your thoughts, and any ideas you have on how we can better deliver the best possible PaaS.

And most importantly, thank you to all of our customers for their support, product usage, and continuous feedback. We love working with each of you and plan to continue to earn your trust and make good on our “No Infrastructure” vision so we can run your infrastructure (so you don’t have to) for many years to come.

Aptible’s New Look, and the future of PaaS

At Aptible, we’re always focused on making it easier for engineering teams to manage their cloud infrastructure. This month, we’re excited to introduce a new set of features designed for better management of user permissions as you scale.

We are excited to announce Granular Permissions for fine-tuning user access on the Environment level! Formerly, Aptible had a simple read/write permission scheme, but as part of this release, we've introduced 2 new read permissions and 6 new write permissions, which can be assigned using Custom Roles. 

This month, we provisioned our 100,000th database! We feel extremely grateful for the teams using Aptible (

). To celebrate, we want to celebrate what we've all accomplished together. In 2022, the teams using Aptible provisioned:

While Aptible did the work behind the scenes:

 we've ever had in a single year, and a 2023 roadmap designed to make magic happen. ✨

This month, we’re excited to introduce a new set of features designed for better management of user permissions as you scale.

What’s new with Aptible: Feb 2023

At Aptible, we are committed to building the platform as a service that grows with your company—from start to scale. Today, we’re excited to continue to deliver on that commitment by announcing Granular Permissions, a new and improved permission model which allows fine-tuning User access.

Until now, Aptible had a simple but powerful system: read-only or full write-access to a given Environment. The simplicity of this system for role-based access controls enabled developers to avoid more complex and error-prone IAM systems, like AWS’s. As teams scaled on Aptible, we saw some of the ways this system was too simple for complex use cases. Some examples include:

To make Aptible work even better for teams at scale, we’ve introduced Granular Permissions for Custom Roles. When implementing, we recommend considering the following so you can ensure your team has the right level of permissions:

“We’ve tested and implemented Tunnel Only permissions. This works great for locking down database access by providing tunnel access without sensitive information like database credentials. It gives us much more flexibility in what we can do!” - DevOps Engineer @ 

Users are assigned Roles which define the level of access they have within your Aptible account. The three types of Roles on Aptible:

TIP: As you scale your team, Custom Roles become more useful for maintaining least-privileged access. Since Roles define what Environments Users have permissions to, we highly recommend multiple Environments to design a least-privileged access principle.

To give Users read permission to a given Environment, you can assign one of the following permissions: 

To give Users write permission to a given Environment, you can assign the following permissions: 

TIP: You can also set up monitoring for key security events like Database Tunneling and SSH Sessions. 

To get started using our new permissions, navigate to the Roles tab within the 

Want to see a new permission be added in the future? 

For a comprehensive list of what’s next with Aptible, and to request features that would benefit your growing team, visit 

Introducing Granular Permissions: For Fine-Tuning User Access

At Aptible, we’re always focused on making it easier for engineering teams to manage their cloud infrastructure. This month, we’re excited to introduce a new set of features designed for greater reliability and security.

. Twingate is a modern alternative to VPNs, enabling you to securely access Apps, provide an additional layer of security to your Endpoints, and adopt and maintain a Zero Trust networking model. Twingate can be deployed in minutes—we did it in 7 minutes—and is free to try. They’ve even put together a guide on how to set it up with 

This month, we’re excited to introduce a new set of features designed for greater reliability and security.

What’s new with Aptible: January 2023

Twingate Integration

See what else is new with Aptible

Coming Soon

More Posts

Aptible’s New Look, and the future of PaaS

What’s new with Aptible: Feb 2023

Introducing Granular Permissions: For Fine-Tuning User Access

Focus on innovation.
Not Infrastructure.

Product

Resources

Support

Company

What’s new with Aptible: January 2023

Twingate Integration

See what else is new with Aptible

Coming Soon

More Posts

Aptible’s New Look, and the future of PaaS

What’s new with Aptible: Feb 2023

Introducing Granular Permissions: For Fine-Tuning User Access

Focus on innovation.Not Infrastructure.

Product

Resources

Support

Company

Focus on innovation.
Not Infrastructure.