Skip to main content

Anniversary starting prices are live.

See Pricing
ZENERA LABS
Zenera Labs Engineering PortfolioInternally developed · MVP

Internal Developer Platform

A self-service platform where developers scaffold services from golden-path templates and provision environments through mandatory, audited policy checks.

Platform EngineeringDeveloper ExperienceDevOps Automation

Built by sanjay · AI Engineering Associate

Login / role selection
01See It In Action

The system, up close

Real captures from the running system — the demo, screenshots and architecture come first, then the deep dive.

Demo

End-to-end walkthrough: scaffold a service, provision an environment, watch a policy rejection.

Internal Developer Platform demo (scaffolding, provisioning, policy rejection)

The demo shows the self-service flow and the 7-layer policy guardrails in action.

Screenshots

1 / 6

Login / role selection
Login / role selection

Architecture

Internal Developer Platform architecture: auth → RBAC → service catalog → templates → policy guardrails → provisioning → audit trail
Policy validation sits between authentication and provisioning with no bypass path.
02The Problem

Why this needed to be built

Teams running 40+ microservices lose days to service onboarding: ticket handoffs, manual config, inconsistent templates and no audit trail.

Developers wait 2–4 hours just to provision a service, policies get bypassed, and nobody has clear visibility into who owns what.

03The Zenera Solution

What we built, and how it changes the workflow

We built a self-service developer platform — FastAPI backend, React dashboard — where services are registered in a catalog, scaffolded from approved templates, and provisioned only after a 7-layer policy check, with every action audited.

Developers register and scaffold services from golden-path templates (FastAPI, Express) that generate source, tests, Dockerfile and CI/CD config. Every provisioning request passes seven guardrails — role, environment, template approval, template-env, naming, resource limits — with no bypass path, then runs PENDING → VALIDATING → APPROVED → PROVISIONING → COMPLETED.

RBAC enforces four roles server-side; an immutable audit trail records every action; the dashboard shows live stats and recent activity. Compared to manual onboarding, registration is ~95% faster and provisioning ~97% faster.

Core design principle

  • Policy validation sits between auth and provisioning with no bypass
  • RBAC enforced on every API endpoint, server-side
  • Every action written to an immutable audit trail
04Key Capabilities

What it can do

A focused set of capabilities that define the system — no marketable filler, only what actually runs.

01

Service Catalog

Register, view, search and filter services with persistent data.

02

Golden-path scaffolding

Generate FastAPI/Express projects with tests, Dockerfile and CI/CD from approved templates.

03

Self-service provisioning

Request environments through a full approval pipeline.

04

7-layer policy guardrails

Role, environment, template, naming and resource-limit checks before any provisioning.

05

RBAC

Four roles (Admin, Platform Engineer, Developer, Viewer) enforced server-side.

06

Audit logging

Immutable trail of every action with user, role, result and reason.

07

Developer dashboard

Real-time stats and recent activity.

05How It Works

The end-to-end workflow

The system processing path, in order.

  1. 1

    Sign in (role)

    Admin, Platform Engineer, Developer or Viewer.

  2. 2

    Register service

    Add a service to the central catalog.

  3. 3

    Scaffold

    Pick an approved template; project + tests + Dockerfile + CI/CD are generated.

  4. 4

    Request environment

    Submit a provisioning request for dev / staging / prod.

  5. 5

    Policy check

    Seven guardrails run; violations are rejected and audited.

  6. 6

    Provision & audit

    On approval, artifacts are created and the whole flow is logged.

06Technology

Stack & tech choices

Backend
Python 3.11, FastAPI, SQLAlchemy, Pydantic
Database
SQLite (WAL)
Frontend
React 18, TypeScript, Vite
Testing
pytest, FastAPI TestClient
07Validation

Tested, verified and honestly scoped

Validation & tests

52 tests across 8 classes cover CRUD, RBAC, policy bypass, scaffolding and audit isolation; happy and failure paths verified.

  • 52 tests: auth, catalog, templates, provisioning, policy, RBAC, scaffolding, audit
  • Developer production-provision rejected and logged; no resources created
  • Viewer cannot provision (403); unauthorized requests return 401

Security & hardening

  • No secrets committed (.env gitignored)
  • Server-side RBAC on every endpoint
  • Policy-before-provisioning with no bypass; Pydantic input validation; CORS allowlist

Honest limitations

Internal Developer Platform is an internally developed engineering prototype. We state limitations rather than overclaim production readiness.

  • Local sandbox only — creates project files, not real cloud infra
  • SQLite, not production-scale
  • Header-based auth; JWT/OAuth is future work
  • No real CI/CD connection or multi-tenancy
08Documentation

Deep-dive references

Documentation

Architecture reference for the platform.

09Future Extensions

Where this can go next

Realistic next steps we've scoped — not aspirational marketing copy.

  • Real cloud provisioning (AWS / GCP / Azure)
  • Kubernetes operator for scaffolded services
  • Git integration (auto-create repos)
  • Multi-env promotion dev → staging → prod
  • OIDC / SAML authentication
  • Multi-tenancy

Have a similar workflow?
Zenera Labs can build a custom version for your business.

This is one of sanjay's internally developed systems. Tell us about your requirement and we'll scope a tailored build around it.