Skip to content
Hiram Mendiola

Capabilities

One person, the whole stack.

Grouped by what it lets me build rather than by logo. Not every project needs all of it — the point is that a single person can cover the range without a handoff losing something in the middle.
01Toolset

What I work with,
and what it’s for.

01

Web & Frontend

Interface engineering with a design sensibility — type systems, motion, accessibility and performance treated as one problem.

  • React
  • Next.js
  • TypeScript
  • JavaScript
  • Tailwind CSS
  • GSAP
  • Three.js
  • Framer Motion
  • Astro
  • Vite

02

Mobile & Desktop

Products that live outside the browser — cross-platform mobile apps, iPad interfaces built for in-person use, and desktop software with local processing.

  • Flutter
  • Dart
  • iOS
  • iPadOS
  • Electron
  • FFmpeg
  • OpenCV

03

Software & Product Engineering

Application architecture, APIs and data models. The systems work that makes a product hold together past its first release.

  • Node.js
  • NestJS
  • REST APIs
  • WebSockets
  • PostgreSQL
  • MySQL
  • MongoDB
  • System Design
  • Integrations
  • AI Integrations

04

Cloud, Deployment & Infrastructure

Everything between a finished build and a working product — servers, routing, certificates, domains, mail, and the debugging that happens at 2am.

  • AWS
  • Lambda
  • EC2
  • Route 53
  • Vercel
  • Serverless
  • Ubuntu
  • Linux
  • Nginx
  • Apache
  • Docker
  • VPS
  • SSL / TLS
  • DNS
  • SMTP
  • SPF / DKIM / DMARC
  • CI/CD
02Production layer

The part that runs
after the build.

Most projects don't fail at the code. They stall in the gap between a finished build and a working product — the servers, records and certificates nobody scoped. That gap is work I take on.

01

Serverless & cloud

Applications deployed to managed platforms where that's the right answer, and to raw infrastructure where it isn't.

  • AWS Lambda
  • Amazon EC2
  • Serverless architectures
  • Vercel
  • Application hosting
  • Production deployments

02

Linux & server administration

Hands-on with Ubuntu production environments — provisioning, configuring and debugging them from a shell.

  • Ubuntu Server
  • SSH
  • Provisioning
  • systemd services
  • Process management
  • Permissions
  • Log inspection
  • Production troubleshooting

03

Web servers & reverse proxies

The layer between a request and an application: routing, caching, compression and static delivery.

  • Nginx
  • Apache
  • Reverse proxies
  • Virtual hosts
  • Domain routing
  • Redirects
  • Compression
  • Caching
  • Static assets

04

DNS & domains

Domain configuration and migrations, including the records most people only meet when something has already broken.

  • AWS Route 53
  • A / AAAA
  • CNAME
  • MX
  • TXT
  • SRV
  • Nameservers
  • Subdomains
  • Domain verification
  • DNS migrations

05

SSL & HTTPS

Certificates provisioned, renewed and kept from expiring quietly on a Sunday.

  • SSL / TLS
  • HTTPS
  • Let's Encrypt
  • Certbot
  • Certificate renewal
  • Secure production domains

06

Email infrastructure

Transactional email that reaches an inbox instead of a spam folder — which is a DNS problem more often than a code problem.

  • Transactional email
  • SMTP
  • Email APIs
  • Domain-based email
  • MX configuration
  • SPF
  • DKIM
  • DMARC
  • Deliverability
03How we work together

A clear path
from first call
to launch day.

Every project follows the same structure. No surprises, no scope ambiguity — you always know where we are and what comes next.
  1. 01

    Discovery

    We talk about what you need, who it's for, and what success looks like. I ask the questions that save us both time later.

    Scope, timeline, and a clear proposal
  2. 02

    Design

    Wireframes, then high-fidelity screens. You see and approve every surface before a line of code is written.

    Approved designs and interactive prototype
  3. 03

    Build

    I engineer the product — frontend, backend, integrations. You get weekly progress demos, not status reports.

    Working software you can click through
  4. 04

    Launch

    Servers, domain, security certificates, email, analytics — I handle all of it. You go live with zero guesswork.

    Live product, fully configured
  5. 05

    Support

    Post-launch monitoring, updates and the occasional change request. I stay on so the product stays healthy.

    Ongoing maintenance and priority support

Most projects take 4–8 weeks from kickoff to launch. Complex builds may take longer — I'll give you a realistic timeline in our first conversation.

Need someone who can do all of it?

Most projects don't need a team of specialists. They need one person who can hold the whole thing in their head and take it to production.