Computed live in your browser via the Performance API. Nothing here is sent anywhere: check DevTools → Network yourself.
View this page's source →
I run P4inz Interactive Labs on my own from Navi Mumbai, India. It makes desktop apps, two Linux operating systems and developer tools, and I take on freelance web work alongside that.
I used to think I'd have to choose between software and 3D. I don't anymore: noticing the small things that are off is useful in both.
The short version
Software came first, and it started the usual way: taking apart things I owned until I understood them, then trying to fix or replace what annoyed me. Windows tools first, then small utilities, then products with actual users.
That became a studio in 2025. It has had three names since, and the current one is the same handle everything already ships under.
3D came in because software alone wasn't covering everything I wanted to make. I started a B.Sc. Animation program at D. Y. Patil University in 2025, which mostly gave a name to something I was already doing on the side.
Kanvaz exists because of that overlap: a reference tool I built for VFX artists because I'm one of them, not something I built to look interesting from the outside.
Almost everything I build ends up privacy-first and offline-first, usually without me planning it that way going in. Nexus doesn't sync to a cloud. Mission OS doesn't phone home. Pursue OS is for investigators who can't afford to leak metadata about who they're researching.
Even this site runs on Cloudflare with nothing beyond Cloudflare's own privacy-preserving traffic beacon: no analytics script, no tracking pixel.
I do all of this alone, so there's no one to catch what I miss and no one to help me move faster either. Some things take longer because of that. Other things stay more consistent than they would with five people making five different calls on the same product. Most days I think that trade is worth it.
Studio names
Ship log
Obsidian Labs, early Windows tooling, and the start of a B.Sc. Animation degree at D. Y. Patil University.
Kanvaz opens its repository on the 13th, then 3D Ref Skills (20th), Reference Engineering (22nd), Glint (24th) and Veris (29th).
Nexus's public release repo opens on the 6th, Obscura on the 8th, Mission OS on the 21st and CrossPort on the 28th. Northbyte Studios becomes the studio's second name mid-year.
MINK opens on the 8th and ships v1.0.0 on the 24th; Pursue OS opens on the 9th; Mission OS ships an Open Beta, then pauses. Project Ascent goes from first playable to a full 25-level campaign in about a week. The second year of the degree starts, and this portfolio moves to Astro.
The studio becomes P4inz Interactive Labs. DRAFT opens on the 5th. Veris jumps to v1.2, Pursue OS returns to active development with a candidate ISO passing automated boot validation, CrossPort ships v1.1.1 and v1.1.2 (29 and 30 Sept) and Kanvaz reaches v9.7.0.
What I believe
Every line here holds up if you read the installer copy, the ship notes, or the source for any product on this site.
Mission OS, Nexus, Kanvaz, Veris, Obscura, Glint and CrossPort ship without telemetry, and each project's own page or README says so. Where a product touches the network at all, it's an update check or a download, not a report about you.
Check itKanvaz README · Mission OS README · Privacy page
Mission OS switches its sysctl hardening and Rust system services on during install, with no post-install script to remember. Nexus seals your files with AES-256-GCM and Argon2id. Security is applied automatically where the product supports it, not left as a manual checklist for afterward.
Check itMission OS README · Mission OS page
Before I ship an update to this site, I check the claim against the real README or release notes. If something's only a concept preview, it says so. I've delayed a ship before because a status label on /status was already out of date.
Check itEditorial policy · Changelog
The products, the case studies, this site's design system, the Mission OS demo, the résumé. One person, start to finish, because that's just how the timeline worked out.
Check itSite source on GitHub · Work
Mission OS, Kanvaz, Pursue OS, Obscura, Glint, MINK, 3D Ref Skills, CrossPort and Reference Engineering are open source. Veris is free on npm (veris-cli). Nexus is the one commercial product, and it doesn't get a telemetry exception either.
Check itLicense list · Support page
For investors + collaborators
Every number below is checkable, against the repos, or against the changelog on /status.
I'd rather ship a few privacy-first products properly than a bigger pile of half-finished ones. A lot of "growth" advice assumes ads and telemetry are free to add. I don't want to build on that.
Nexus is the main commercial product, an encrypted vault for Windows. Mission OS is the bigger, slower one: a privacy-first Linux distro built at OS scale, currently paused after its Open Beta. Kanvaz and Obscura are free and open source on purpose. Everything else supports one of those.
Right now, the most useful thing is introductions: to other founders, investors, or open-source maintainers who care more about the product being right than about growing fast. I'm not chasing growth marketing, an agency handoff, or a full team.
Current stack
I don't have one favourite language. I have projects that each demanded the right one and I picked deliberately. The chips are generated from the project data, so they always match what's really built with what.
For Windows-native products
WPF is the least-glamorous choice a modern .NET dev can make, and the right one for Nexus. Native windowing, real ClearType, no Electron bloat, integrates with Windows Hello and the Credential Manager the way users expect. Chose WPF over Avalonia specifically because Nexus ships Windows-only for now and I wanted to lean into the platform, not abstract it.
For desktop tooling
Glint runs on Avalonia: native, no Electron, sub-second cold start. It ships for Windows, where the WMI and DDC/CI monitor control it depends on lives. WPF muscle memory transfers over cleanly.
For Kanvaz
Kanvaz needed to run everywhere a VFX artist works, and its whole surface is a canvas full of references: HTML5 canvas + drag-and-drop APIs mapped to that better than any native alternative. Vanilla JS on purpose: no framework churn, easy for anyone to fork and extend.
For systems-level products
Rust runs Mission OS's system services and is the language of Pursue OS, MINK (a compiler with its own native code generator, no external toolchain), CrossPort and DRAFT.
For Mission OS
Building an OS you want to trust means starting from something already trusted (Debian Stable) and building deliberately on top of the most polished free desktop environment (KDE Plasma). The installer is Calamares, customised with Mission OS branding and a Python post-install module that applies the hardening automatically.
For Project Ascent
One codebase exporting to Windows, macOS, Linux and the browser (playable on itch.io), with 18 automated test suites including a full 25-level reachability sweep.
For engineering-side tooling
For static content sites
This portfolio was a single 15.9MB HTML file through v4.7. It worked, but every edit meant scrolling through one enormous document. Astro gives me component-scoped CSS, real routes, and zero JS by default, and it deploys to Cloudflare Pages without any extra config.
Identity
Working with me
I take on independent client work in web development, UI/UX, branding, and 3D/VFX visualization, one or two new projects at a time. Scope tends to be one of three shapes:
Fixed price for short-loop work. Weekly for longer builds. Never per-hour. Everything I ship uses the same discipline you see across my own products: privacy-first, no telemetry, clear about what a first version can and can't do. If that fits what you're trying to build, start a conversation.
Contact
Ask about the work
Answers from what's shipped