{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
{
}
<
>
/
0
1
;
=
(
)
[
]
#
{
}
The person behind the products

I ship. I run. I don't stop at the demo.

Builder-operator, not a slideshow founder.

I'm a vibe coder who builds and operates real products end to end — design, code, infrastructure, and the 2am pager duty when something breaks. Vibe coding means I describe what I want, steer the result, and ship it fast. If it's live, I built it and I'm still watching it.

My work spans two worlds that most people keep separate: products built for real customers, and autonomous bots that run on their own. Webformer is live and open for business. Nexa proves the second works, running live every day.

No agencies, no ghost teams. I vibe-code the products, tune the systems, and own the outcomes.

What I actually do

Vibe Coding

Turning plain-language ideas into working products fast, then running them in production.

Live Systems

Bots that run on their own, safety switches, and systems that keep improving themselves.

Full-Stack Product

From database schema to billing to the pixel-level UI users touch.

Ops & Reliability

Monitoring, uptime, and the discipline to keep systems running under real load.