James Carlo Rivera000

I design and build complete systems for real operational problems — from the interface to the server they run on.

Products,not demos.

Batangas, Philippines4th-year BSIT · PUP Sto. TomasOpen to internships & product engineering roles
Featured system 02KonektadoView case ↗
Scroll

(01) — Statement

Portrait of James Carlo Rivera

I build complete systems for real operational problems — from the interface to the server they run on. Product decisions, architecture, real users, and interfaces careful enough that nobody notices the plumbing. Most of my projects started as an operational problem in a business I could actually walk into.

00System in real operations
00In development or ongoing
2027BSIT, PUP Sto. Tomas

(02) — Selected systems

9 projects — full index ↗

(03) — Path

2021 — present
2026

Konektado

Undergraduate thesis · in development

A barangay-oriented mobile platform matching residents with local workers through service categories, roles, location and verification signals.

2025

FlowPress

Built and deployed at CJNET

The QR upload and print path for the shop, revised after watching how it was actually used.

2024

Homelab

Self-hosted infrastructure

Linux, Docker, Nginx and Cloudflare routing. Where deployment became something I operate.

2023

Polytechnic University of the Philippines

BSIT · final year

Coursework in systems, networks and databases, strengthened through projects built beyond the classroom.

2021

CJNET Computer Shop

Family business · operations

Support, networking, print workflow and internal tools—and the environment that tells me which problems are worth building for.

Next

Avera

Future direction

A product studio focused on practical software for workflows and communities I understand firsthand.

(04) — Stack

By depth, not by count
Used in substantial projectsThings I have shipped or deployed something real with.
ReactReact NativeExpoNext.jsTypeScriptJavaScriptTailwind CSSPHPSupabasePostgreSQLDockerLinuxNginxCloudflareVercelMikroTikGit & GitHub

(05) — How I work

Four steps, one feedback loop
01

Observe

Standing at the counter watching where the queue actually breaks—not asking anyone what they need.

02

Define

The workflow gets written before the stack does. Most ideas die here, which is the cheapest place to die.

03

Build & deploy

AI agents help with implementation. I own the requirements, architecture, integration, validation and the environment the system runs on.

04

Watch & revise

Real use is the test. I watch where people work around the system, then rebuild around what they actually do.

The judgement is the job. The typing is not.