Designed and built the core product experience for Beauto, an AI-powered automation tool for small businesses.

What I did:

AI Assistant — chat interface where users describe a task and the AI builds the automation, with proactive, impact-ranked suggestions

Integrations hub — searchable library of one-click connections (Calendar, Stripe, HubSpot, Slack, etc.)

Analytics dashboard — automations run, hours saved, and conversion rate at a glance

Result: A chat-first flow that felt far less intimidating than traditional automation builders in user testing, driving most new automations created.

So creative 👏

New work: I rebuilt my studio site as a real-time 3D experience, then I attacked it.

The visual layer is hand-written WebGL and GLSL. GPU particle cores that react to your cursor, morphing transitions between pages, adaptive performance that tunes itself to the device. All custom code, no template, no page builder.

But looking expensive is only half the job. I also build and secure the systems behind sites like this: multi-tenant SaaS, Stripe billing, PostgreSQL row-level security. So I wrote an automated red-team loop in Python and ran it against my own live site: attack, triage, patch, verify. It flagged a couple of hardening gaps, I fixed them, and re-ran until it came back clean.

If you want a site that looks like a high-budget trailer and holds up when someone probes it, that is what I build.

Live: xkaii.studio The security work: xkaii.studio/security

The combination of high-end GLSL motion and row-level security backend is incredible. What vulnerabilities did your automated Python red-team loop flag during the initial test runs?