Matin ZandiProduction Case Studies
← Portfolio
PRODUCTION CASE STUDIES

What I deployed.How I operate it.

These case studies focus on infrastructure behavior: service isolation, deployment flow, persistence, health checks, recovery and the practical lessons behind operating multiple workloads safely.

6production / infra projects
Dockerisolated service stacks
HTTPSreverse-proxied exposure
Healthverification before confidence
SECURITY NOTE

Public case studies intentionally omit secrets, private IPs, credentials and internal-only implementation details while preserving the infrastructure story.

Selected systems

Each visual area is ready for a real product screenshot. Until then, the fallback is clearly presented as an architecture/product preview — never as fake evidence.

AgentYar real panel screenshot
AGENTYAR / ARCHITECTURE PREVIEW
01 / AGENTYARPRODUCTION + STAGING

AgentYar

AI-agent platform operated as separate production and staging stacks, with API/worker separation and dedicated state services.

What I implemented

  • Separate production and staging deployments.
  • API and background worker separation.
  • PostgreSQL and Redis as isolated state services.
  • Container health checks and local-only application ports.

Operational lesson

Staging only helps when it is truly isolated. Shared ports or data services can turn a test change into a production incident.

Pattern: Internet → Caddy/TLS → localhost API → containers
State: PostgreSQL + Redis   Workers: background processing   Env: production / staging separated
LinuxDocker ComposeAPIWorkerPostgreSQLRedisStaging
RastaYar real panel screenshot
RASTAYAR / PRODUCT PREVIEW
02 / RASTAYARPRODUCTION

RastaYar

Remote-support platform deployed as an isolated application behind HTTPS with local service exposure and health-aware operations.

Infrastructure focus

  • Application service exposed only to localhost.
  • Caddy handles public HTTPS and reverse proxy.
  • Containerized deployment isolates lifecycle from neighboring apps.

Operational lesson

A shared VPS stays manageable when every project has a clear directory, Compose project, port and ownership boundary.

Pattern: Browser → HTTPS → Caddy → localhost service → container
Rule: no public app port, no shared Compose lifecycle
DockerCaddyHTTPSVPSReverse Proxy
TicketYar real panel screenshot
TICKETYAR / PANEL PREVIEW
03 / TICKETYARPRODUCTION

TicketYar

Ticketing platform with application API, worker processes, PostgreSQL persistence and readiness-aware deployment.

Infrastructure focus

  • API and worker services separated by responsibility.
  • Persistent PostgreSQL data layer.
  • Readiness checks used before trusting the service.

Operational lesson

A container being Up is not the same as the application being Ready.

Pattern: HTTPS → API → PostgreSQL   |   background workers
Verify: readiness endpoint + application reachability
APIWorkersPostgreSQLReadinessDocker
SiteYar real panel screenshot
SITEYAR / PRODUCT PREVIEW
04 / SITEYARPRODUCTION

SiteYar

Website-builder stack split into web, API and worker services with PostgreSQL and Redis.

Infrastructure focus

  • Next.js web service separated from FastAPI backend.
  • Worker service separated from request-serving API.
  • PostgreSQL + Redis as dedicated data services.

Operational lesson

Service separation makes failures easier to locate and restart independently.

Pattern: Web → API → PostgreSQL / Redis
Async: worker consumes background tasks independently
Next.jsFastAPIPostgreSQLRedisWorker
TradeYar AI real dashboard screenshot
TRADEYAR AI / DASHBOARD PREVIEW
05 / TRADEYAR AIPRODUCTION

TradeYar AI

AI trading platform with API/worker separation, PostgreSQL/Redis persistence and a backup path.

Infrastructure focus

  • API and background processing run independently.
  • PostgreSQL + Redis persistence.
  • Backup service separated from normal request traffic.

Operational lesson

Backup is not an afterthought; recovery needs to be designed before the incident.

Pattern: API + worker → PostgreSQL / Redis
Recovery: backup path separated from application traffic
APIWorkerPostgreSQLRedisBackup
DevOpsYar real monitoring screenshot
DEVOPSYAR / OPERATIONS PREVIEW
06 / DEVOPSYARLAB / DEPLOYED

DevOpsYar

Operations-focused stack exploring synthetic checks, alerts and service visibility.

Infrastructure focus

  • Monitoring-oriented web/API services.
  • Synthetic checks and alert-oriented components.
  • PostgreSQL + Redis support services.

Operational lesson

A server being reachable does not mean the application path works.

Pattern: Web + API + Redis + PostgreSQL
Ops: synthetic checks + alerts   Focus: observability and failure visibility
MonitoringSyntheticAlertsDockerLinux

How these projects connect to my career

My professional base is support and infrastructure. These projects extend the same operational mindset into Linux, containers, automation, isolation, health checks, backups and observability.