Building Oberik: the agent layer you drop into your SaaS. Per-customer isolation, cited answers, your own model keys. Free while we launch.
Turkey
Joined March 2014
- Tweets754
- Following96
- Followers84
- Likes368
web pki has this incredibly weird idea of what a certificate authority is
i can prove that i own example.com. acme already lets me turn that proof into a cert for *.example.com. everyone agrees that im authorized to control tls for basically anything underneath that domain
x.509 even has a mechanism for the obvious next step: give me a constrained cert that can only sign for names under .example.com, and let me issue my own leaf certs. cryptographically, this is completely normal. the browser verifies the chain, the name constraint prevents me from doing shady stuff. i gain no authority over anyone else's names
except web pki looks at me signing a certificate for foo.example.com and goes **holy shit, you're a certificate authority now**.
apparently i have not merely exercised authority over a namespace that i already own. no. i have entered the sacred profession of cert issuance. now we are talking audits, compliance, policies, ops reqs, so the whole ca apparatus
meanwhile dns has somehow figured this out. if i own example.com, i can delegate foo.example.com to somebody else. i can let them create arbitrary records beneath it. nobody concludes that ive created a new domain registrar. nobody demands that the operator of foo.example.com comply with the registrar reqs because they can create names below a namespace that was explicitly delegated to them
but certs?
"you may control every hostname under this domain."
"great, can i sign certs for those hostnames?"
"absolutely fucking not. that would make you a ca."
and tomorrow ill rant about why we needed a second global trust hierarchy in the first place when we already had a hierarchical namespace that could publish its own damn keys
Derin İlkcan Karakoç retweeted
I'm 30. I built an AI startup called @GojiberryAI doing over $4M ARR in one year. Got accepted into YC.
No one wants to hear this, but there's no magic distribution channel.
We got there by experimentmaxxing one channel at a time, based on our MRR level.
$0 → $6k MRR: pure outbound. Cold email + LinkedIn, using our own early product on ourselves. No brand, no audience — just us reaching out to people showing intent and starting conversations. Ugly, manual, effective.
$6k → $25k MRR: Reddit. Our first real acquisition breakthrough. We posted educational breakdowns in SaaS subreddits and pulled 10M+ organic views. Traffic quality wasn't amazing, but the volume flooded our trial funnel for months. Cost: basically zero.
$25k → $75k MRR: content + free blueprints. All-in on LinkedIn content, YouTube, motion-design videos, and giving away our internal systems as free "blueprints." Content got the reach, blueprints earned the trust, and a chunk of readers converted. This is where founder-led content started compounding.
$75k → $150k MRR: partnerships + X. We added Twitter, B2B influencers, sponsored newsletters, and a lifetime affiliate program that became a major lever. We also joined YC around here — the intensity went vertical.
$150k+ MRR: paid + hiring. Meta ads, Google ads, influencer agencies, and our first serious hires: growth, sales, engineering, product.
To get to $1M+/month, it’s mostly going to come down to hiring the right people and putting the right structure in place.
Here's the part people miss: none of these stages replaced the last one. They stacked. Outbound never stopped. Content never stopped. We just added the next lever once the current one was clearly working.
If you take one thing from this: don't chase five channels at once.
Beat one until it works. Then add the next.
needed something for a product im building, found out its forbidden by web pki policy for reasons i couldnt justify, so instead of changing the product i emailed the standards body responsible for the rules asking why the rule exists
software development is going great
Derin İlkcan Karakoç retweeted
We didn’t choose SSH as the default way for agents to interact with Oberik because it sounded smart.
Agents already know how to interact with shell, and machines already know how to secure it.
So we gave them the door they already know how to open
for three years we built AI products for clients. about a dozen projects, different sectors, different sizes
every one wanted different business logic. every one needed the same backend underneath. we wrote it from scratch every single time
the thing i was most stubborn about: you bring your own model keys
requests route through your credentials. usage bills to you at your provider's price. nothing resold, no markup, and you can self-host the whole stack. i did not want to be another company between you and your model provider
it went live yesterday. zero users outside the client projects we used it on. no payment gateway connected, nothing to buy for now
what i want is people who build something real on it and tell me where it broke #buildinpublic
oberik.com
