Marko Krečković (@mkreckovic) header
Marko Krečković (@mkreckovic) profile picture

building ragentis: oss ai frontend infra // ai stuff // coffee always

Joined April 2010
Photo by Marko Krečković (@mkreckovic)Photo by Marko Krečković (@mkreckovic)Photo by Marko Krečković (@mkreckovic)Photo by Marko Krečković (@mkreckovic)Photo by Marko Krečković (@mkreckovic)Photo by Marko Krečković (@mkreckovic)Photo by Marko Krečković (@mkreckovic)Photo by Marko Krečković (@mkreckovic)Photo by Marko Krečković (@mkreckovic)
you can build ai agents, but if your systems and data are a mess you end up automating chaos, so step 0 is getting the plumbing right. what's your step 0 before you let agents touch anything?
3
5
231
wrapped up the final .env.example for ragentis. it's onboarding disguised as config. its basically a mini spec now: what's allowed, what's recommended in dev, what's recommended in prod. if a new dev cloned your repo today, what's the first env var they'd have to ask you about?
3
224
markdown is the lowest-friction contract between people and tooling. what's your default format?
2
125
marketing is the part where reality shows up. where did reality show up for you this week?
1
4
128
when i'm about to subscribe to a tiny SaaS, i check the team. not because i care where they went to school. just to see if there's at least one engineer. it's not even a "vibe coding is bad" take. i like vibe engineering, we all use shortcuts. but if the product is shipped by someone who doesn't really understand the code they're shipping, i get nervous.
1
4
106
clawdbot is so viral that i don't even see the posts anymore. too much reach can kill the read.
5
115
one trick that helped me: stop describing the product yourself and let users do it. ask "what would you tell a friend this does?" and your positioning usually shows up in their words, not yours.
3
4
127
working on ragentis security today. goal: secure-by-default baseline, without requiring an extra proxy layer. // ship log rate limiting: toggle + headers + per-user keys. health: optional ip allowlist. api: no-store caching. cors: warning on risky config.
1
1
6
190
exactly this. "don't install clawdbot if: - you've never used a terminal before - you don't understand API keys and tokens - you're not comfortable with linux basics - you can't budget $50-100/month for experiments - you're not prepared to read documentation - you want it to 'just work' out of the box"
1
124
we did a deep tech mvp that took 2 years and only after shipping did it hit us, the real work was the conversations we skipped. if you are not talking while you build, you are basically guessing your positioning and demand.
1
2
82
building an auth plugin for ragentis right now. vue + typescript folks, what auth framework do you recommend? i'm currently looking at better-auth, talk me into or out of it.
4
117
note from wearing too many hats at once: Being founder, designer and engineer at the same time is weird. You see the story, the pixels and the database in the same frame. Some days that feels like a superpower. Other days it feels like three people arguing in your head. The only thing that helps me is writing. Once I put the story into words, the design and the code get a lot simpler. Priorities line up. Trade-offs get clearer. It's like deciding who gets to drive today.
5
2
141
We spent two years building "git for design". Illustrator + Photoshop integrations. A text-based format that stayed 100% compatible with Adobe. Git-friendly, diffable. Each version stored only the real change. Then we hit the harder part: the human workflow. Designers don't want branches and merge conflicts. So we built a visual git that made sense to designers. The scar: deep tech isn't just hard to build. It's hard to make feel obvious.
2
100
we built git for design. developers were in disbelief, like "wait… is this actually a real repo?" "can i pull it?" "what does a merge conflict look like in illustrator?" under the hood it was a real git repo, plus our layer that generates an adobe-compatible design file that's text-based, so diffs, commits, branching, merging all worked inside illustrator. designers mostly just wanted their usual workflow back.
2
120
The best setup I've seen for a lot of AI and deep tech teams is not "Europe or US". It is both, on purpose. Build the core team where you can get continuity. Where people stay long enough to finish the hard parts. Where the company can survive the months that look boring from the outside. And stay close to the market where distribution is dense. Customers, partnerships, capital, the conversations that move faster in person. This is not easy. Time zones are real. Context loss is real. "Who owns what" gets messy if you're not careful. But when it works, it compounds. You get an engine team that does not reset every six months. And you get a go-to-market surface area that is hard to replicate from far away. Hybrid is not a compromise. It is a strategy for founders who know their product has a long fuse, but still needs reach.
1
2
76
a vibe-coded app looks done until it hits an edge case, security issue, or deploy break. then you're the on-call dev. self-hosting already eats time with updates and migrations. add a one-off codebase with no upstream fixes and it becomes a quiet time sink. and i'm saying this as someone deep in ai and a senior dev: without deliberate architecture + ongoing oversight, ai alone still doesn't ship something that stays correct, secure, and maintainable. main question: who owns bugfixing, security, and hosting when the person prompting can't read the code?
3
83