Studio Pro Tech Update · Self-Host Hub

Kawika Ohumukini

28d ago (edited) in Tech-Talk

Studio Pro Tech Update

Hi. I've been coding the SaaS application and I wanted to give an update.

Studio Pro is 3 modules; Live, API and Workers. I built it with these goals:

The whole system is a standalone SaaS application built on a robust framework (Studio API) that anyone can use to spin-up their own automation service for themselves or others. That means taking into account installation, maintenance, support, payments, subscriptions, and complying with the various licenses by the apps and AI models that the system could use. It will have workflow management and a database to replace services like airtable and make.com and n8n for the supported workflows. Payments and subscriptions are TBD so stay tuned.

It will be open-sourced using the MIT license so you're free to "...use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software...".

LIVE - The Frontend Layer has to be lightweight, deployable as standalone or in an orchestrator like Kubernetes and be brand-able using templates or custom designs. The front-end is a visual interface to the API which provides the main functionality like signup, creating api keys, storing secrets for other APIs, workflow management, etc. n8n would be at this layer.

API - The API layer has to be multi-tenant (organizations), use modern methods like websockets, webhooks, API Keys and HMAC signatures, granular permissions (video:write, service-account:read), multiple user roles (super-admin, admin, member), accept and issue API calls, queue management for worker tasks, fully tested, worker cluster management, deployable standalone or in an orchestrator, etc. The Postgres database is at this layer.

WORKER - The Worker Layer has to be horizontally scalable, fast to spin-up, highly performant, state-of-the-art features and be rooted in keeping costs to a minimum if not zero$.

We have brainstormed some really cool ideas like an airtable/make/n8n migration tool and AI workflow builder, ComfyUI API integration for advanced effects, and much more.

I attached images of the high-level flow and test coverage report. Anyone that knows code testing knows that 100% test coverage (every single line has a test) is usually a distant dream that is rarely obtained. But, I've been a software engineer and site reliability engineer for 40 years and my standards are very high.

The last couple months, I've written just under 10,000 lines of code and I haven't made enough time to post the tutorials and demos I want to do and I'll do better in the coming days and weeks. I appreciate your patience and support.

Cheers

4 comments