About — my story

Chapter 1 — The itch

I’ve always shared tiny scripts with friends and teams: “drop a file here, get magic out there.” Every time, the same chores showed up — packaging, setup, permissions, “it works on my machine.” The script was the easy part; everything around it was the exhausting part. I wanted a place where you can rent your logic without giving it away.

That seed became Functory: ship your code privately, let others execute it safely, and if it’s useful, you earn when it runs. No slides. No fluff. Just useful compute.

Chapter 2 — The first builds

I kept things simple and focused on feel: when you hit Run, you should see life instantly. So I built a runner that saves your execution environment the first time and safely reuses it after. The result is fast first-byte on subsequent runs, consistent outputs, and no “surprise drift.”

Artifacts are handled for you, logs stream in real time, and your code stays private by default. The goal is quiet reliability — tools that disappear so you can think about the problem, not the plumbing.

Chapter 3 — Principles I won’t compromise

• Privacy-first: your code stays yours; only execution is exposed.
• Reproducibility over vibes: same inputs, same environment, same outputs.
• Fair metering: simple, transparent usage; creators choose a per-second margin and an optional fixed fee.
• Ownership: Functory is rails, not a destination. You keep the IP.
• Simple beats clever: fewer moving parts, fewer surprises.

Chapter 4 — The human bits

I’ve been coding since I was 12. Over the years I’ve built (and broken) thousands of projects — a lot in quantitative finance: backtests, tick-data pipelines, risk dashboards, execution bots. Honestly, writing code is my passion; it’s still my favorite way to think.

I love technology and I bike a lot — long rides reset my brain and spark ideas. I am optimistic about technology. I believe that by working together to develop technology and pooling our knowledge, we can build a wonderful world :) I’m building for tinkerers: the ones who paste a script and suddenly ship a product.

Chapter 5 — What’s next

Short term: smoother run feedback, sturdier downloads, and friendlier onboarding. Medium term: team workspaces, better insights for creators, and a playful referral system that rewards useful functions, not vanity metrics.

Long term: a world where “I scripted this” instantly becomes “people can use it” — safely, privately, and at any scale. If that resonates, you’re my people.