A developer-first ticketing SDK built as a learning project by a cloud engineering student — designed to look, feel, and behave like real production infrastructure.
Our mission
Tickitz exists to explore what world-class developer tooling looks like — clean APIs, typed SDKs, sensible error handling, and documentation that actually helps you ship.
Too many ticketing systems are clunky, poorly documented, and painful to integrate. This project asks: what if someone built it the right way, with developers as the primary user?
Every design decision in Tickitz — from the 9 specific error classes to the atomic check-in endpoint — is intentional and inspired by the best developer tools available today.
The person behind it
I'm a B.Tech Computer Engineering student at MBIT, with a deep focus on cloud computing and system architecture. I architect scalable backend systems, containerized infrastructure, and seamless CI/CD pipelines — turning complex cloud problems into elegant solutions.
My hands-on stack includes AWS, Docker, Kubernetes (learning), Node.js, MongoDB, Flutter, and Linux. I'm actively exploring cloud system architecture to design systems that scale from idea to production.
Beyond academics, I've shipped real products: CitySolve won 1st Prize at CVUM Hackathon — a GovTech platform that digitises civic issue reporting with AI-powered duplicate detection. Infera automates document management for Kochi Metro Rail, processing 1,200+ documents daily at 98.7% accuracy. EnviroMine tracks carbon emissions for mining operations with AI-powered insights.
Tickitz is my exploration of what a production-grade developer SDK looks like — built the right way, designed with care, shipped as a real npm package.
Tech stack
What drives Tickitz
Every API surface, error message, and piece of documentation is written with the developer's time in mind. If it takes more than one line to integrate, it's not done.
Complex systems — queues, fraud detection, distributed check-in — should feel simple from the outside. The SDK handles the hard parts so you don't have to.
HMAC-signed webhooks, scoped API keys, OTP authentication, SOC 2 design principles — security isn't an add-on, it's the foundation everything else is built on.
Every design choice in this project is documented and intentional — a way to demonstrate what good developer infrastructure looks like, and to learn by building it properly.
Auto-retry with exponential backoff, typed errors with request IDs, 99.99% SLA design targets — even a learning project should be built as if real users depend on it.
PPP-adjusted pricing in 50 countries, edge-runtime compatibility, multi-region architecture — good infrastructure should work for everyone, regardless of geography.
Journey
Started with HTML/CSS, JavaScript, and the basics of backend development. Built the first projects — EnviroMine and early prototypes — to understand how systems actually connect.
Dug deep into Node.js, REST API design, MongoDB, and authentication patterns. This is when the idea of building a full SDK started to form.
Shipped two major projects: Infera for Kochi Metro Rail and CitySolve — winning 1st Prize at CVUM Hackathon. These validated that real-world systems were within reach.
Began serious study of AWS architecture, Docker containers, and distributed systems. Started to understand what production-grade infrastructure actually requires.
Building Tickitz as a complete, production-quality SDK and web platform. The goal: demonstrate mastery of developer tooling design, TypeScript SDKs, and modern web UI — all in one project.
This website and the Tickitz SDK are built entirely for learning and portfolio purposes. Tickitz is a personal project created by Vrajkumar Parekh to demonstrate skills in developer tooling design, TypeScript SDK architecture, API design patterns, and modern web UI development.
No production guarantee is given. While this project is designed to look, feel, and behave like real production infrastructure, it is not intended for use in any real-world, commercial, or mission-critical application. The API, SDK, and all associated services may be unavailable, incomplete, or subject to breaking changes at any time without notice.
No warranty of any kind is provided — express or implied — including but not limited to merchantability, fitness for a particular purpose, or non-infringement. The author accepts no liability for any direct, indirect, or consequential damages arising from the use or inability to use this software.
All pricing, statistics, company names, and testimonials shown on this site are fictional and used for demonstration purposes only. Any resemblance to real organisations or products is coincidental.
Built by Vrajkumar Parekh · Source on GitHub · For portfolio & learning only
Whether you want to collaborate, hire, or just talk cloud infrastructure — I'm always open to a conversation.