Arcane Labs / portfolio index

Arcane Labs00
Open to work — 2026

I build systems people can rely on.

I'm Jayesh Sudhakar, a systems engineer and technology consultant in Australia. I work from the core implementation through to the product experience: AI systems, security tooling, browser-native 3D and personal software. I care about the work that makes a system trustworthy in practice — clear boundaries, resilient architecture and a deliberately simple experience. I take on systems-engineering roles, AI integration work, and consulting and selected builds through Arcane Labs.

BasedAustralia — remote
FoundedArcane Labs — 2026
FocusSystems · Security · AI
StatusOpen to work

01 Selected work

Products and systems, built end to end.

A private, macOS-first AI system that works across projects with native OS-level access — without sending work through someone else’s server.

The hard part: giving a model useful reach into an operating system without giving it unrestricted control. Sage is being built around scoped permissions, sandboxing and an audit trail, so capable automation remains accountable.

Why it mattersUseful AI needs context and the ability to act, but important work should not require handing every file and decision to a remote service. Sage explores how capable assistance can remain private and accountable.
Current statePrivate early build, macOS first.
Focus areas
on-device AIprivacyagentsOS integration

An AI-driven personal organisation system for the moving parts of everyday life: academics, scheduling, finance, meals and career planning. Named after the Roman goddess of the hearth, Vesta is designed to be a calm center that stays in step with the life around it.

The hard part: personal systems only earn trust when they are useful enough to return to and clear enough to stay in control of. Vesta combines structured planning with machine-learning-assisted insights, while keeping important actions reviewable.

Why it mattersLife is usually split across calendars, notes, banking apps, meal plans and job trackers. Vesta brings those decisions into one connected view, helping surface what needs attention instead of making you maintain another set of lists.
Current stateWorking privately as a browser-based early build.
Focus areas
personal systemsmachine learningfinancial toolingplanning

An in-development private-networking system for Android and macOS: a self-hosted WireGuard mesh, optional exit-node routing, LAN-device monitoring, tracker filtering and connection diagnostics.

The hard part: each capability normally arrives as a separate product. Numen keeps them under one trust model, with a shared Rust core and thin platform layers rather than five disconnected tools.

Why it mattersMost consumer privacy products solve one narrow problem at a time and ask for trust without showing their trade-offs. Numen is built around a clearer model: your own devices, your own infrastructure and visibility into what the network is doing.
Current stateRust core components are built and tested; Android and macOS wiring, live mesh enrollment and infrastructure deployment are still in progress.
Focus areas
WireGuardRustself-hostednetwork monitoring

A shipped Python command-line scanner for web applications you own or are authorised to test. It crawls pages and forms, then runs a focused set of OWASP-aligned checks across headers, TLS, cookies, CORS, redirects, traversal, XSS and SQL injection.

The hard part: useful findings need context. Argus captures baselines before testing, reports severity and evidence, exports JSON, and returns CI-friendly exit codes rather than treating every signal as equally urgent.

Why it mattersSecurity issues are cheaper to address before release than after a customer, attacker or audit finds them. Argus gives developers a practical first pass they can run on authorised targets as part of the build process.
Current stateShipped as a Python CLI with eight implemented check modules and structured JSON reporting.
Focus areas
web securityOWASP-alignedCLICI

A live, playable early-build 3D open world that runs entirely in a browser tab. There is no launcher or download: follow a link and enter the experience.

The hard part: the frame budget. The world uses instanced rendering for dense asteroid fields and keeps its game loop lean, because a browser has nowhere to hide a slow load or uneven frame time.

Why it mattersInteractive 3D is often locked behind downloads, launchers or specialist hardware. Voidpath makes the first experience as simple as opening a link, while still treating performance as a core part of the design.
Current stateLive and playable; multiplayer architecture is documented but not yet part of the build.
Focus areas
WebGLstreamingframe budget

A direct-to-consumer storefront for an organics brand — catalogue, cart, a four-step checkout, server-side payment session creation, pincode validation, and consignment tracking through a serverless proxy. A partial build is deployed; it isn't taking orders yet.

The hard part: not the storefront — the loyalty economics behind it. Any rewards scheme can be modelled into insolvency. This one was costed per product category, with the loss cases written down before a line of it shipped.

Why it mattersA commerce build is more than a storefront. It needs a checkout customers trust, operational links to fulfilment, and incentives that still make sense when real orders and margins are involved.
SurfaceWeb — partial build deployed
Focus areas
paymentsserverlesslogisticsunit economics

02 Voidpath — playable

Browser-native 3D

An open world with no install.

A live, browser-native 3D world built solo and still early in its development. Every asset and frame is budgeted because there is no launcher to hide the loading behind.

RuntimeBrowser
PlatformDesktop
Target60 fps
StatusLive
— Playable
Playable build

Runs right here in the page. Loads only when you ask, so it never costs you a frame before then.

Built for desktop — open on a larger screen to play

WebGL · loads on demand Open fullscreen →
New tab Running · Esc to stop

03 Argus — demo replay

Most scanners bury the finding that matters under forty that don’t.

Argus tests a target you own for common web vulnerabilities across a focused set of OWASP-aligned checks. The output below is a recorded replay against a deliberately vulnerable demo host — not a live scan, and not your machine.

argus — zsh Replay

04 PureHarvest — in development

Commerce that holds up beyond the first click.

A D2C storefront for an organics brand — catalogue, cart, a four-step checkout, server-side payment sessions and consignment tracking. The loyalty economics were modelled to the point of failure before a line of it shipped.

StageEarly build
ProductD2C
ScopeFull storefront
DirectionB2B expansion
— Preview
Deployed build

A partial build, deployed and browsable. Not accepting orders — the storefront and checkout are real, the shop isn't open.

Storefront preview Open in new tab →
New tab Live session

05 What I bring

What I bring to a project.

Six places I am useful, and the work that proves each one. Not a list of tools — the judgement that decides which tool belongs, what the thing costs to run, and what happens when it fails at three in the morning.

01

Systems, end to end.

Most failures do not live in the components. They live in the seam between them.

Numen runs one shared Rust core under thin Android and macOS layers, so a change to the trust model lands once rather than three times. The architecture is the thing that decides whether the second year of a project is cheap or impossible.

In practice — Numen

02

AI systems that can be trusted with access.

Capability without boundaries is not intelligence. It is unaudited risk.

Sage gets scoped permissions, sandboxing and an audit trail before it gets broader operating-system reach. On placement at Digital Technology Solutions I design the system prompts that govern an agent's logic, tone and safety limits — the part that decides what a model is allowed to be wrong about.

In practice — Sage · DTS

03

Security treated as a build habit.

A finding costs hours before release and weeks after it.

Argus runs eight OWASP-aligned check modules, captures a baseline before every payload so a response has to actually change to count, gates on severity and returns CI-friendly exit codes. I also do vulnerability research on Bugcrowd and similar platforms, which is where you learn what real targets actually look like.

In practice — Argus · bug bounty

04

Performance as a design constraint.

Speed is not a polish phase. It decides what the thing is allowed to be.

Voidpath is an open world running in a browser tab with no launcher to hide a slow load behind, so every asset and frame is budgeted and the renderer uses instancing for dense fields. If the experience is expensive, the experience has to earn it.

In practice — Voidpath

05

Shipped, deployed, and still standing.

A build that was never deployed is a prototype with good intentions.

This site runs on Cloudflare Workers with D1 behind a static front, its own telemetry, origin checks and a content security policy. Deployment, hardening and the boring operational edges are part of the work, not a separate job handed to someone else afterwards.

In practice — ARC-1 · this site

06

The commercial side of a build.

A feature can work perfectly and still lose money on every order.

PureHarvest's loyalty scheme was costed per product category and modelled to the point of insolvency before a line of it shipped. I ran my own e-commerce store before that, which is where the difference between a working checkout and a profitable one stops being theoretical.

In practice — PureHarvest · Stella's Toy Garden

06 Stack

What I bring to a build.

A practical toolkit for taking a product from a hard technical problem to a working experience. The value is not a list of technologies; it is knowing where each one earns its place.

01

Languages & core

  • JavaScript & TypeScript
  • Python
  • Rust
  • HTML, CSS & UI systems

02

Web & real-time 3D

  • WebGL & Canvas
  • Interactive product experiences
  • Design-system CSS
  • Frame & asset budgeting

03

Infrastructure

  • Cloudflare Workers
  • Serverless APIs & deployments
  • Git & CI workflows
  • Native platform integration

04

Security

  • OWASP-aligned testing
  • Threat modelling
  • WireGuard mesh networking
  • Network visibility

05

AI systems

  • AI integration & automation
  • Agent permissioning
  • Private model workflows
  • Audit trails

06

Commerce

  • Payment-gateway integration
  • Checkout systems
  • Logistics & tracking APIs
  • Unit-economics modelling

07 Services

Built for startups that need one person to cover a lot of ground.

Client work runs through Arcane Labs, my independent studio. Early-stage teams rarely need a specialist for every layer — they need someone who can carry a problem from the business case through to something deployed, and say honestly which parts are worth building at all.

011–2 weeks

Startup build advisory

Before the build: what to make first, what to cut, what it will cost to run, and whether the thing earns money once it works.

Scoping an MVP that can actually ship Unit economics modelled before incentives go live Technical direction, stack choice and build order

Built it first — PureHarvest, Stella’s Toy Garden

022–6 weeks

AI systems & automation

Local-first AI, capable agents connected to the tools you already use, and automation that removes repetitive operational work.

Agents wired into your existing systems Local and private deployments, no data leaving your machines Document, intake and reporting pipelines

Built it first — Sage, Vesta

031–3 weeks

Security engineering

Finding meaningful security risks early, then helping build the systems and tooling that address them.

OWASP-aligned review of an app you own Hardening: secrets, auth, session and transport Interfaces and tooling for security products Vulnerability research on Bugcrowd and other platforms

Built it first — Argus, Numen

043–8 weeks

Interactive & 3D web

Product and brand experiences with real-time browser graphics, designed to stay fast and accessible on everyday devices.

WebGL product and brand experiences Configurators and interactive explainers Performance work on 3D that already exists

Built it first — Voidpath

054–10 weeks

Commerce, built to make money

A storefront with payments, logistics and tracking, supported by unit economics that are modelled before incentives go live.

Storefront, checkout and payment integration Shipping, tracking and fulfilment plumbing Loyalty and pricing modelled against margin

Built it first — PureHarvest

062–8 weeks

Web & product engineering

Fast, considered websites, product interfaces and dashboards that are designed around what the business or user actually needs to do.

Websites, dashboards and internal tools Interactive product flows and serverless APIs Production-ready hosting and deployment

Built it first — Vesta, PureHarvest

074–12 weeks

Game development

Real-time interactive builds and the maintenance that follows them — browser-native worlds, game systems and the performance work that keeps them playable.

Browser and desktop game builds Gameplay systems, tooling and live maintenance Performance and frame-budget work on existing games

Built it first — Voidpath, plus ongoing client work

084–12 weeks

Native applications & systems

Desktop and mobile product work where performance, system integration, privacy and reliable deployment matter as much as the interface.

macOS and Android product architecture Rust cores with platform-specific integration Secure local-first system design

Built it first — Sage, Numen

08 ARC-1 — prototype

Leave the important parts with ARC-1.

I built ARC-1 as my personal Keeper of Threads — a quiet intelligence, an echo at the edge of my attention. He receives a first signal, gathers the pieces that matter, and keeps their shape intact so the conversation has weight and direction. By the time I step in, there is already a thread to follow.

Please relay your enquiry to him, and he will make sure the thread reaches me with its shape intact.

ARC-1 channel —— record 0%

Your details stay inside this private enquiry flow and are used only to respond. ARC also records minimal operational telemetry — page activity, device class, approximate network region, referral origin and session time — to protect the site and improve the path. No advertising or mailing-list sign-ups.

Ready to turn a hard problem into a working system?

Hard problems are the ones worth taking: AI systems with real access, security work that has to hold, native and interactive builds, and the deployment that makes them someone's Tuesday rather than a demo. Bring the difficult half.

Leave it with ARC-1 → Book a call →
Jayesh Sudhakar — Arcane Labs · 2026 Built from scratch. No template.