I'm a Software Developer with a strong full-stack background, now deepening into Cloud, DevOps, and Platform Engineering.

Over the last few years, I’ve built APIs, dashboards, internal tools, and production-facing applications. More recently, I’ve been leaning harder into how do these systems actually get deployed, observed, scaled, and operated under real constraints. This shift has pushed me toward infrastructure, runtime environments, failure domains, observability, and the operational side of software delivery.

• Designing a platform-first homelab to develop real infrastructure and operations skills through meaningful workloads
• Building Ceiba, a Node-first API productization layer that helps teams add API keys, plans, quotas, usage tracking, and subscription-gated access to an existing API without adopting a full gateway.
• Exploring Linux, storage architecture, container orchestration, observability, and deployment discipline
• Focusing on reliability, failure handling, and operational clarity, not just feature delivery

Node-first API productization layer for existing APIs.

Ceiba is focused on helping developers and small teams:

• protect endpoints with managed access control
• issue and manage API keys
• define plans and quotas
• track usage
• gate access through subscription-backed rules
• avoid standing up a full gateway or building the entire access stack in-house

It also serves as a meaningful workload for validating platform and deployment decisions.

(In progress) Production-inspired platform designed to explore infrastructure, observability, and workload operations.

• RAID1 boot resilience with dual EFI
• Storage isolation across OS, runtime, database, and backups
• Platform-first design before workload sprawl
• Current direction includes k3s, Prometheus, Grafana, Loki, and CI/CD
• Built around failure-domain thinking, recoverability, and operational clarity

Hackathon-built launchpad for turning an endpoint into a paid, agent-ready tool package.

MonetizeAPI takes a simple API or endpoint description and generates the pieces needed to package it for monetization:

• pricing and quota recommendations
• x402 payment metadata
• MCP tool definition
• Ceiba-ready policy config
• docs and launch checklist
• paid-call simulation
• downloadable launch package

It was built for the Agnic monetization track, using Agnic for OAuth, balance, top-up, and paid model calls while keeping the core product logic provider-independent.

Longer term, MonetizeAPI is the alpha path toward Ceiba Launchpad: a guided layer that helps developers move from having and endpoint or service to a priced, protected, documented, agent-callable product.

Full-stack campus platform deployed on Azure Kubernetes Service.

• Next.js, Node.js, PostgreSQL
• Firebase Auth (Google + Microsoft)
• CI/CD with GitHub Actions
• TLS with cert-manager (DNS-01 challenge)
• Blue-Green deployment strategy

• Designing Failure Domains on a Single Node: Boot, Platform, Data, Backup Tiers

• From Null to Tenant: Dynamic SSR Fetching with Orval, Next.js, and ASP.NET APIs

• Dynamic Theming at Runtime: Tailwind + CSS Variables for Tenant-Specific Branding

-> Visit my Blog for more

Portfolio

Building systems that are not only functional — but observable, reliable, and operable.