Machi / Web

Machi Web and Shared Python Backend

The Web client and shared backend for Machi, a city-life community platform covering posts, housing, second-hand listings, jobs, messages, notifications, membership and media upload.

Web BetaProduct design, full-stack architecture, Web client, Python API, database, deployment and operations

Tech Stack

Next.jsReactTypeScriptPythonSQLiteSSEREST APIAWS

My Role

Product design, full-stack architecture, Web client, Python API, database, deployment and operations

Problem

Web, iOS and Android needed to share the same data facts while keeping platform-specific interaction patterns.

Solution

I centralized accounts, feed, posts, messages, notifications, media and membership in one API, with compatible DTOs for all clients.

Result

Built the foundation: 80+ REST + SSE endpoints, 19 tables, media upload, soft delete, cursor pagination and multi-client sync.

Overview

Machi is a city-life community product I build and run solo. The Web client uses Next.js, while a Python backend exposes the shared API used by Web, iOS and Android.

My Role

Product planning
Next.js Web client
Python REST + SSE API
Database design
AWS / Nginx / systemd operations

Problem

Multi-client DTO stability
City / language / content filters
Media delivery
Realtime messages and notifications

Solution

Shared API for core facts
Compatible DTO fields
Object storage and CDN
SSE for lightweight realtime updates

Architecture

Background

Machi is a city-life community product I build and run solo. It brings housing, second-hand listings, jobs, local services, Q&A, messages, notifications and membership into one city space.

My Role

I handle product planning, Web development, the shared backend, database design, API contracts, deployment and operations.

Stack

Web: Next.js / React / TypeScript / Tailwind CSS
API: Python REST + SSE
Data: SQLite, designed with a PostgreSQL migration path
Ops: AWS / Nginx / systemd / object storage / CDN

Takeaway

Machi Web taught me that full-stack work is not just writing frontend and backend. It is keeping users, data, permissions, media, notifications and deployment reliable inside one product.