Unity engineering
Runtime systems, editor tooling, rendering constraints, and architecture that stays readable under pressure.
01 / Foundations
Long-lived software, built deliberately.
A Wabi-Sabi approach to engineering.
Production-grade tools, developer systems, and purposeful applications, with ongoing research in computational topology. Designed and built by Vav-Labs in Turin, Italy.
TURIN, ITALY / COMPUTATIONAL TOPOLOGY RESEARCH / 2026-05-14
Production diagnostics
Profiling-first workflows for bottleneck isolation, risk reduction, and shipping decisions grounded in evidence.
Technical publishing
Documentation, product positioning, and case-study writing that helps tools look credible before they scale.
02 / Tools
01 / tool
BugLens / SceneLens
Unity editor tooling for finding, documenting, and communicating scene-level issues faster.
- Inspector-first debugging workflow
- Scene context and reproducible issue notes
- Asset Store-ready documentation and support model
02 / tool
In progressUnity Production Tooling
Small, focused tools for teams that need cleaner workflows around debugging, validation, and release checks.
- Practical editor UX
- Low-friction project integration
- Built for maintenance, not demos
Published products
Public Google Play presence acts as shipping evidence, not as a decorative logo row.
The site should make it easy to verify that Vav Labs ships, maintains, and supports real software. That signal matters now, even before the content model expands into dedicated product and case-study pages.
03 / Case studies
Engineering proof should read like decisions under constraints, not portfolio theatre.
Each case study in this phase is still a compressed signal. The layout needs enough structure to hold future expansion, but the current page must already communicate systems thinking clearly.
01 / study
Rendering architectureSDF Raymarcher URP
Explore signed-distance-field rendering inside Unity URP while keeping the implementation understandable and measurable.
Unity URP HLSL C#
Shader architecture, screenshots, and technical write-up planned.
02 / study
Frame budget recoveryMeta Quest VR Performance
Investigate CPU/GPU bottlenecks under mobile VR constraints and prioritize changes that protect frame timing.
Unity Quest URP Profiler
Before/after timing notes and optimization checklist planned.
03 / study
Editor tooling productBugLens / SceneLens
Turn a recurring production debugging pain into a clear Unity tool with docs, support boundaries, and product positioning.
Unity Editor C# Tool UX
Product page, demo flow, and documentation planned.
04 / study
Maintainable systems designRustyArchive / RavenCap Systems
Design data and runtime systems that can grow beyond prototype code without losing clarity.
C# Architecture Data workflows
Architecture notes and repository links planned.
04 / Notes
Notes stay compressed for now, but the structure already needs to feel publishable.
The one-page version should hint at the future content model without pretending those articles already exist. The layout needs to support calm, technical reading from the first release.
01 / note
PlannedHow I structure Unity projects that outgrow MonoBehaviour scripts
A practical boundary-first approach for projects that need to stay testable and readable.
02 / note
PlannedURP performance mistakes I look for first
The first rendering and pipeline checks I make before deeper optimization work.
03 / note
PlannedHow to build a Unity Asset Store tool without exposing source
Packaging, documentation, support, and source-protection tradeoffs for tool publishers.
05 / Contact
Vav Labs is a technical brand for production-ready Unity work.
I work on Unity systems where maintainability matters: editor tooling, runtime architecture, rendering experiments, optimization workflows, published apps, and production recovery.
The next stage is multipage. The current responsibility is simpler and stricter: make the homepage precise enough that the later split into tools, studies, and notes feels like expansion, not repair.