This release is BIG if you are spinning up cloud resources dynamically from your application. Read on! App environments run in a cloud account (say AWS) that belongs to you or your customer. For each app environment you spin up using LocalOps, a dedicated network is provisioned in a specific

As we head for our launch in Product Hunt and other communities later this quarter, we wanted to make LocalOps platform self serve and super obvious for developers to get started with. So our team doubled down on Developer documentation past week. And wrote a ton of example code, documentation,

Tuesdays are always special for us. We work from 3 different timezones and we come together on a single channel on every Tuesday to make new releases. Last week, we introduced QA role. Account owners can invite Developers and QAs within LocalOps to spin up App environments in their cloud

We want to make it easier for you (developers) to not just deploy applications on "any cloud" (your cloud or your customer cloud / Private SaaS) but also want to let you handle customers of "any size". It could be a medium size business in Europe with

🎉 We shipped two new capabilities this time! First, we made it easy for you to create identical app environments with identical infra configurations, using Environment Templates. What are Environment Templates? You get to define commonly used compute, network, storage configurations of your environments as "Environment Templates". Whenever you

Yup, we kept our weekly release promise. You can now invite your team members in your LocalOps account to do private cloud deliveries. You can assign them either Administrator, Operations or Developer role. How can someone think about these roles? Here is how - Developers can build apps & releases

We made a release today. Thats new, to start with! We are making it a habit at LocalOps to ship every Tuesday. There it goes on our Basecamp schedule: As for today, lets start with some appetizers. If you signed up for LocalOps and created your brand new "app