Frontend
Nuxt
Vue
TypeScript
Digital product studio
Digital products, built to work.
Websites, applications and business systems — designed and engineered as one product.
In the work
- Nuxt
- Vue
- TypeScript
- Node.js
- AdonisJS
- PostgreSQL
- Docker
- MinIO
The studio
One practice for the screen and the system under it.
A storefront, a mobile product, an operations panel, an API — we treat them as one build. From the first interface to the release, the decisions stay in the same room.
- 01 Storefront
- 02 Mobile
- 03 Operations
- 04 API
Selected work
Real products. Real builds.
Browse the catalog in the device it was made for. Live preview opens the project when a public URL exists.
01 / 06
Ham Sakhteman. 01 / 06
01 / 06 Web Apps
Ham Sakhteman
A building management app that stays simple, secure, and modern.
What we build
The product, and the system that keeps it running.
Six kinds of work. Each one is designed and engineered, not delivered as a picture of a product.
All services01
Websites
High-performing brand, marketing, and content websites with strong typography, SEO structure, and fast user journeys.
02Web Applications
Product interfaces, dashboards, portals, and real-time workflows designed to make complex tasks feel simple.
03Mobile Applications
Focused iOS and Android experiences with clear interaction patterns and product thinking from the first screen.
04E-commerce
Storefronts and commerce systems for curated catalogs, smooth checkout flows, and data-informed growth.
05Admin Panels
Internal tools that respect real operations: permissions, workflows, reporting, and dependable day-to-day speed.
06Backend Systems
APIs, data models, integrations, and service foundations that keep products secure, maintainable, and scalable.
How the work moves
A full product cycle, kept small enough to stay sharp.
We stay with the work from the first questions through release, and after it meets real use.
01
Understand
We learn the business, the people using it, and the constraint that actually matters before drawing a screen.
02
Design
Flows, interface, and content are decided together, so the product has a shape engineering can build.
03
Build
We implement the system: interface, data, and the paths between them, with the release in mind.
04
Launch
We ship, watch the first real use, and fix what only shows up outside the studio.
05
Evolve
After release we stay close enough to tighten the product where people actually get stuck.
Engineering
A stack we can stand behind.
The tools change with the product. The standard does not: a clear interface, dependable data, and a release we can operate.
Backend
Node.js
AdonisJS- APIs
Data
PostgreSQL
MongoDB
Infrastructure
Docker
Nginx- Object storage
A serious build
If the product is worth building, let’s talk about what it has to become.
Tell us who it is for, what it has to do, and where it is stuck. We will say plainly whether we are the right studio, and what the first useful step is.
- Who it is for
- What it has to do
- Where it is stuck