India · Available worldwideatiUjjwal
Independent practice / IndiaSoftware engineer · Systems builderOpen for select builds

atiUjjwal

The work of Ujjwal Kashyap

Built with
care. Made
to last.

Production software for hospitals, schools and hospitality.

Explore
the work
Editorial portrait of Ujjwal Kashyap against a paper collage
Fig. 01 / Engineer & builderOne person. End to end.
Thoughtful software. Everyday infrastructure.Meet the person behind it ↓
01

Who you'd be working with

THE PERSON
BEHIND THE BUILD.

Close portrait of Ujjwal resting his face on his hand
Ujjwal Kashyap / India · Remote

I build the software institutions actually run on.

Full-time software engineer, and the person hospitals, schools and hotels call when they need a system that has to work every single day. Appointment booking, school management, hospitality operations — designed, built and shipped end to end.

I'm Ujjwal Kashyap, the software engineer behind ati ujjwal. I work full-time on production systems and build high-end web platforms independently on the side. My work is not brochure sites. It's the booking desk a hospital opens at 8am, the fee ledger a school closes at month end, the front desk a hotel runs a full season on.

That means I care about the unglamorous parts: uptime, data integrity, how the thing behaves on a five-year-old phone with two bars of signal, and what happens when the person using it has thirty seconds and a queue in front of them. I take a project from the first conversation through architecture, build, launch and the months after it — one person accountable, no handoffs.

3

Production systems live

3

Industries served

Multi-tenant

Architecture by default

< 24h

Response commitment

02

Selected work / A working portfolio.

WORK

A live index of shipped platforms, case notes and system diagrams — the kind of work institutions quietly rely on.

Open Portfolio
Ujjwal in an architectural collage of systems and paper structures
Selected systems / Designed, built & shipped end to end
02.1

Systems I’ve built and run.

4 systems / 2 live
Start a conversation
03

Behind the interface

Ujjwal working at his laptop in an editorial paper collage
At the desk / The unglamorous parts matter

BUILT TO
KEEP GOING.

A note on engineering

What happens
after launch?

Uptime. Data integrity. A five-year-old phone with two bars of signal. A person with thirty seconds and a queue in front of them.

These are the conditions the software has to work in.

  • 01 Multi-tenant architecture
  • 02 Role-scoped access
  • 03 Isolated deployments
Ujjwal considering a problem at his desk
Think it through. Then build it.
04

From first conversation to the months after

One person.
The whole build.

Architecture, build, launch and the months after it — one person accountable, no handoffs.

Ujjwal at a worktable of plans and architectural models
The product / Start with the work it needs to do

The booking desk. The fee ledger.
The front desk. Real work, made easier.

A collage of Ujjwal planning, building and reviewing his work
The process / From a conversation to a working system
  1. 01 / Understand

    The first conversation. The institution and the people using the system.

  2. 02 / Build

    Architecture, implementation, and the details that keep data in the right hands.

  3. 03 / Stay accountable

    Launch, operations, and the months that follow.

Full-length portrait of Ujjwal among cut-paper compositions
Independent by nature

A little character.
A lot of care.

A playful cut-paper portrait of Ujjwal with stars and geometric shapes
05

Security & data privacy

Built for data that can't go wrong.

The systems I build hold patient appointments, student records and payment details. That data belongs to the institution and the people it describes — never to me, and never to a third party I quietly signed up on your behalf. Each deployment is isolated, access is role-scoped, and nothing leaves the system to feed analytics, advertising or model training.

Encrypted in transit Role-scoped access Isolated deployments Named administrators
Editorial portrait of Ujjwal alongside illustrated servers and connected systems
Architecture / Accountability / Ownership

Honest by default

Specifics over badges. Accountability over noise.

All traffic is served over HTTPS with modern TLS, so data is encrypted in transit between the browser and the server. Credentials are stored as one-way hashes and are never recoverable in plain text. Databases are hosted with encryption at rest enabled by the provider, and access is restricted to the application and named administrators. Backups follow the same protections as the live data.

Ask about your stack
06

Contact

Ujjwal looking toward the open space on the left of the composition

Let's talk about what you need built

Whether it's a system for an institution or a product idea you want shipped properly, the fastest route is a direct message. I read everything and reply within a day.

Direct message