Dev Log: 2026-08-05 — reverse proxies, email journeys, and a tenant that wasn't there

On August 5th, 2026, two significant updates rolled out in two different products. The first product, a deployment platform, introduced a tier-3 reverse proxy with a real nginx layer. This new reverse proxy tracks and gates traffic based on the health of the underlying workloads, ensuring only operational systems receive traffic.

Alongside this, the platform now enforces capabilities from provider capabilities via a checklist. If a provider cannot meet the required standards, the platform refuses to execute related operations. Additionally, a standard blueprint library has been introduced, offering MySQL/MariaDB provisioners for easy setup. The integration of release rollback mechanisms allows for a simple return to a previous operational state in case of errors during deployment.

Over on the CRM app side, the feature highlight is the introduction of email automation journeys, commonly referred to as sequences. These sequences allow contacts to journey through timed email steps triggered by specific actions like the addition of a tag or the submission of a form. The design integrates standard pieces such as enums for sequence triggers, step types, and send statuses.

Typed state management with label and color functionalities adds clarity to each step. Listeners are connected to domain events to track the enrollment of contacts at the right moments. The send status syncs with mail events, ensuring accurate tracking of each step's delivery. Every sequence's deliverability is maintained through its own tracked entity, rather than a "fire and forget" approach. This methodology ensures traceability and auditability of the email journey.

However, the update was not without bugs. A notable issue arose where self-registered users were being created without an assigned tenant. This discrepancy caused downstream "create a record" calls to fail, as records had no defined place to reside. The solution was to incorporate tenant assignment during the user creation process, rather than treating it as an afterthought.

This adjustment ensures that when a user is created, they are automatically associated with a tenant, preventing future issues related to tenant identification. In conclusion, two repositories saw substantial improvements today, with both products making meaningful advancements. These enhancements are complemented by a dependency bump elsewhere in the ecosystem, signifying a comprehensive upgrade process.