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
Commercial Unity tool
Asset Store-readyBugLens / SceneLens
Commercial Unity Editor tool for capturing Play Mode bug evidence and exporting structured debugging reports.
- Private source by design
- Markdown, JSON, and AI-ready report exports
- Built for Unity teams that need reproducible bug context
Public engineering work
01 / tool
ShippedGodot Project Doctor Mini
Godot 4 editor plugin for project hygiene diagnostics and export-ready reports.
- Release v0.2.4
- MIT licensed with CI
- Markdown and JSON diagnostic reports
02 / tool
LiveSDF Raymarcher URP
Real-time volumetric raymarching with signed-distance-field primitives in Unity URP.
- Unity URP rendering architecture
- Performance-focused technical demo
- MIT licensed source
03 / tool
ShippedRavencap
Streaming encrypted archive tool for files, folders, and Unix-style pipelines.
- Rust CLI with v2.0.2 release
- age-compatible encryption workflow
- Archive, compression, and verification path
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.