Designing spaces that always stay — built to leave a lasting mark.

Creative development where motion, clarity and craft meet.

00

Loading

Self-Service Blockchain Platform

A multi-tenant SaaS that provisions isolated Hyperledger Fabric networks self-service — collapsing days of manual blockchain infrastructure into a guided 5-step wizard.

BrBPO blockchain provisioning platform
The
Problem

Standing up a permissioned blockchain network — Certificate Authorities, peers, orderers, MSP, channels and chaincode — took days of error-prone manual operations for every organization.

It had to become self-service, fully isolated per tenant, and repeatable

Client
BrBPO
Timeline
2025
Present
Role
Full-Stack
Engineer
Architecture
·
Backend
·
Frontend
·
DevOps

THE IDEA IN NUMBERS

THE IDEA IN NUMBERS

Standing up a permissioned blockchain network — Certificate Authorities, peers, orderers, MSP, channels and chaincode — took days of error-prone manual operations for every organization.

It had to become self-service, fully isolated per tenant, and repeatable

A multi-tenant SaaS that provisions isolated Hyperledger Fabric networks self-service — collapsing days of manual blockchain infrastructure into a guided 5-step wizard

Days→Min

Setup time

Per-org

Tenant isolation

11

Pipeline steps

Fabric v2

Blockchain

K8s

Orchestration

Self-serve

Provisioning

Key
Metrics
Days
Min
Setup
Time

Network provisioning collapsed from manual days to an automated few minutes

Per-org
Tenant
Isolation

Every organization runs a fully isolated Fabric network — one Kubernetes namespace each

11
steps
Deploy
Pipeline

NestJS-orchestrated Ansible pipeline, 11 steps with real-time SSE log streaming

Challenges
01

Isolating tenants so one organization's network can never reach another's, solved with namespace-per-organization on Kubernetes

02

Giving operators clear feedback through a long, failure-prone provisioning flow, solved with an 11-step pipeline streamed live over SSE

03

Automating the Fabric v2 chaincode lifecycle while honoring consortium signature ordering

04

Closing a cross-cluster token-validation vulnerability surfaced during a security hardening pass

Solution

I architected an 11-step deployment pipeline in NestJS that orchestrates Ansible playbooks against the Kubernetes API through the IBM Blockchain Platform Operator, with real-time log streaming over SSE, namespace-per-organization isolation, and provider-agnostic JWT + RBAC auth.

The full Hyperledger Fabric v2 chaincode lifecycle — package, install, approve, commit — is automated with dynamic per-organization YAML via Helm, plus on-chain asset tokenization.

A React/Next.

js front-end exposes a real-time network build viewer and a role-based admin dashboard with full CRUD across every network

Technologies
NestJS
Kubernetes
Hyperledger
Fabric
v2
Ansible
Helm
React
Next.js
TypeScript
CloudNativePG
nginx
Results
&
Impact

Cut blockchain network setup from days of manual work to minutes

Fully isolated Fabric networks provisioned self-service through a 5-step wizard

Real-time build visibility via SSE log streaming

Provider-agnostic auth (JWT + RBAC) ready for Auth0/OIDC

INSPIRED?
LET'S BRING
YOUR
VISION TO
LIFE!

WHATSAPP

+5561991293839

TELEGRAM

@PANDERSOM