This post explores our two-year journey to be a remote, first efficient team, starting with GitHub Codespaces and a recent shift from cloud-based development environments to environments on our laptops.

The Prodvana Runtime Interface is the gateway to customer environments. The Prodvana Runtime Interface ensures that Prodvana is backend-agnostic and helps minimize migration costs for various Runtime types.

The Prodvana Convergence Engine takes the desired states from the Prodvana Compiler and the Service’s current state from the Prodvana Runtime. It continuously makes decisions to converge the current states to their corresponding desired states.

The Prodvana Compiler is responsible for compiling user configurations into a desired state. It is a critical component in implementing intent-based delivery and minimizing migration costs onto Prodvana.

Platform Engineering is a force multiplier for velocity, reliability, and efficiency. This series will outline the learnings we have had building an intent based deployment engine.

Most business validations happen after deployment slowing down organizations. Teams like compliance, legal, security, finance, and even sales, are left to figure out how to validate the business rules they are expecting.

See how we implemented Role Based Authorization Controls (RBAC) at Prodvana, from assessing various SaaS and open-source authz systems to our decision to develop an in-house solution.

Maestro brings sophisticated release strategies to every Service on Prodvana. You can now deploy anything from day 0 apps to months-long stateful-systems deployments.

Engineers expect world class experiences when they are building, running and maintaing software. Prodvana's approach is to create workflows for engineers.

Learn how Prodvana helped Replit move to an intent based deployment system that gave visability and simplicity to engineering teams managing Kubernentes, Virtual Machines, and more.

How often has a missed schema migration caused your application code to break in production?  If that has ever happened to you, this blog post is for you. 

Clairvoyance gives you a personal spidey sense. Know who, what, how, where and when high impact changes were made. Bisect changes quickly to get to root causes in releases.

Prodvana offers an orchestration platform that unifies point solutions streamlining cloud management. Observer Mode and Runtime State Inspector builds on two of our key commitments: unifying your workflows and building self-healing your environments.

By migrating to Prodvana, Doorstead can position itself for the next phase of its engineering and company journey, built on a scalable, efficient, and adaptable production environment. 

The software development landscape has witnessed a surge in the popularity of service catalogs, such as Backstage, Cortex.io, OpsLevel, and Port. These service catalogs have revolutionized how development teams collaborate and organize their development flows. However, they have a significant drawback: they lack a complement for abstracting away and orchestrating software in production.

Two core practices make up the DevOps cycle in DevOps: Continuous Integration (CI) and Continuous Delivery (CD). Their functions are intertwined, streamlining the flow of code from development to production. This interconnected flow leads to the misconception that they represent the same business process and that one technical platform can address both. This blog post aims to debunk this misconception by exploring the unique aspects of CI and CD, highlighting why each requires a specialized technical system.

Based on BCG’s findings and Prodvana’s industry interviews, these tenancy solutions are becoming the industry's dominant architectural patterns for B2B software. We will start by exploring the power of these architectures. Then, we will discuss how convergence-based deployment systems minimize the operational overhead of maintaining and deploying these architectures. The pendulum is swinging from fully optimizing for overhead to a balance of customer needs and operational overhead.

In this post, we'll dive into the powerful capabilities and flexibility of Prodvana's convergence engine. This engine is a critical component of a broader system that brings together configurations from multiple inputs (like services, applications, and environments) to make deployment decisions.

The cloud era gave us shared infrastructure leading to product patterns developed for multi-tenant environments. This architectural pattern drove margins and reduced the operational overhead of managing multiple customers. This post covers the basic architectures of tenancy and outlines best practices for building environments that support different tenancy needs. 

Deployment is at the heart of the engineering process. A practical and robust deployment system enables engineers to ship code faster, more reliably, and spend time on their core competencies instead of debugging infrastructure.

Efficiency is top of mind for everyone in 2023 and will continue to be relevant for the foreseeable future. This post explores how Prodvana can fit into your overall efficiency strategies.

We’re excited to announce that Prodvana recently received our SOC 2 Type 2 compliance report!

Storage systems have very complex requirements for deployment. In this post we explore how Prodvana can make even the most complex deploys simple.

Distributed systems have evolved and require more sophisticated ways to handle deployment. This is the first of a two part series on distributed systems and deployments.

This blog outlines Prodvana’s Golden Path -- our default software path to production. This is how we ship our product to you, our customers. With our golden path, we can onboard a new engineer at Prodvana in 30 minutes and have them deploying code safely in less than 1 hour. 

As a Product Engineer, I’ve seen firsthand how CD systems can slow down product development in growing engineering teams. 

As we’ve mentioned before, CD’s static nature is one of its fatal flaws. Static pipelines treat “delivery” as a discrete event without considering the ever-changing contexts surrounding it — whether it’s infrastructure changes, changes coming from other teams’ deployment pipelines, or changes in user behavior. CD usually misses these signals. 

Have you ever had to look up directions to meet a friend? Then memorized it or written it down? Only to find a roadblock, accident, electrical issues on the tracks, and many other unforeseeable issues.

According to HashiCorp’s 2022 State of the Cloud report, 4 out of 5 companies use or plan to use multi-cloud.

Continuous Delivery & Deployment have three fatal flaws which make them unsuited for modern software delivery.

In Part 1 of this series, I talked about the importance of having a platform strategy and why platforms are ultimately a business strategy. Once you have defined a strategy, the next step is to execute this strategy. Unfortunately, executing a large strategy is rarely ever simple, and plans will have to change and adapt.

How does one go about building platforms? As in most things, the place to start with is the why. In this blog post, I will argue the importance of defining a platform strategy and why platforms are necessarily a business strategy.

I was the tech lead for a project to replace Dropbox’s aging monolith with a modern platform. The monolith story is similar to many in the industry. There were many initiatives to improve the monolith situation, including a company-wide Service-Oriented Architecture (SOA) push a few years prior. These initiatives all failed to make lasting changes due to conflicting incentives and priorities.

In 1996, my parents gave me a Performa 6115 Macintosh for my 15th birthday and a subscription to Dr. Dobbs, a magazine about programming that ended in 2014.