Stratava

Stratava is an internal AestheTeQs automation project created to explore and demonstrate how modern web applications can interact with Make.com-based workflow orchestration.

The project combines a customer-facing or operational web interface with an external automation layer, allowing application events to trigger structured workflows outside the core application.

Rather than embedding every process directly into application code, Stratava demonstrates an integration-oriented architecture in which selected business events can be handed off to Make.com through webhooks and processed independently.

The implementation also integrates with Supabase, giving the application a persistent cloud data layer while Make.com handles workflow orchestration. Connectivity between the application environment, Make.com webhooks, and Supabase was explicitly tested during development.

The project was developed internally to strengthen practical experience with automation architecture, event-driven workflows, webhooks, cloud data services, and low-code orchestration.

Many internal business processes involve repetitive actions that do not justify tightly coupling every step to application backend code.

Typical processes may require an application to receive an action, persist information, trigger an automation, process the event through another service, and continue the workflow without requiring a user to manually perform every step.

The engineering challenge was therefore to create an application architecture where the frontend and data layer could work cleanly with an external automation engine.

Stratava was designed around Make.com as the workflow orchestration layer. Application events can be represented as structured payloads and sent through Make.com webhooks. During development, webhook payloads included identifiers, event types, sources, timestamps, and event-specific data, demonstrating an event-oriented integration pattern.

Supabase provides a cloud-connected data layer while Make.com provides a flexible way to react to application events and coordinate downstream automation.

This provides a practical demonstration of separating core application functionality from workflow automation.

Business Process Automation / SaaS. The technical patterns demonstrated by Stratava are applicable to areas such as:

The project material confirms both the Make.com webhook endpoint and the Supabase service were part of the integration environment.

The important architectural concept is the separation between the application layer, data layer, and automation layer.

The integration uses HTTPS communication between cloud services and keeps automation execution outside the browser-facing workflow.

Webhook endpoints and environment configuration should remain outside publicly exposed source configuration, while validation should be performed before processing external events.

Because this is an internal skills project rather than a regulated production platform, its security is presented as integration hardening and controlled service communication, rather than claiming enterprise security controls that were not part of the project.

The frontend is deployed to Netlify at stratava.netlify.app. The application connects to cloud-hosted services such as Supabase and Make.com rather than requiring the entire automation environment to run on the same server.

Stratava demonstrates a reusable automation pattern:

Its value as an internal project is less about traffic volume and more about demonstrating an integration architecture that can be reused for CRM automation, lead management, notifications, data synchronization, operational workflows, and SaaS products.