marinoseliades

4 ms·

1. 1.▲
   by marinoseliades 2mo ago

   More on this, we're still experimenting between a hard vs. soft paywall. Regardless, if you sign up it should be easy enough to play around with it for a while on the free tier. We promise that we don't send spam/marketing em
2. 2.▲
   by marinoseliades 2mo ago

   Heard, we're actively working on this and should have updated pricing plans soon.
3. 3.▲
   by marinoseliades 2mo ago

   Thanks! Custom beats generic if building it takes days instead of months.
4. 4.▲
   by marinoseliades 2mo ago

   Fair, the generation part is commoditized. What we sell is the trust layer around company data. No credentials in the builder's hands, scoped access per tool, forkability etc. CC + Railway works until someone pastes a prod key into an
5. 5.▲
   by marinoseliades 2mo ago

   Thanks! The private endpoint tip is very much on point. We've already hit two prospects where the blocker was that they don't want full self-host but their security groups won't take generic cloud egress. It's on the lis
6. 6.▲
   by marinoseliades 2mo ago

   You're right, and we don't. The judge is best-effort screening not enforcement. Enforcement is deterministic with per-tool Postgres roles, proxy-injected creds, host allow-list, human approval on destructive writes. Those hold whe
7. 7.▲
   by marinoseliades 2mo ago

   The difference is Retool still basically trusts whoever (or whatever) is building the app, we don't. The agent writing the code never sees a credential and each tool gets its own Postgres role. Even if it generates something dumb it ph
8. 8.▲
   by marinoseliades 2mo ago

   We ended up splitting permissions per-tool for data and per-person for connections, for basically this reason. Every tool gets its own db role that can only see its own schema, and integration credentials live in a broker the tool's co
9. 9.▲
   by marinoseliades 2mo ago

   Closest comp. I'd argue the "AI builds the app part" is fast becoming table stakes. The unsolved problem is what happens after the app exists and that's what we actually built. Anyone in the org can fork a coworker'
10. 10.▲
    by marinoseliades 2mo ago

    Thanks for the feedback. From what we've gathered so far, non-eng are using CC or Codex to build one-off internal tools, but they're deploying them on their personal Vercel accounts and sending the url over Slack. That's the
11. 11.▲
    by marinoseliades 2mo ago

    Today it's GPT-5.6 Luna sitting inline on the egress broker, with Terra re-judging anything Luna flags as ambiguous. We are still experimenting though.
12. 12.▲
    by marinoseliades 2mo ago

    Thanks! That's the best kind of validation. If you ever take Prized for a spin, would genuinely love to hear how it compares to what you built, especially on the data access side.
13. 13.▲
    Launch HN: Prized (YC S26) – Let non-engineer staff build secure internal tools(prized.dev)

    79 points by marinoseliades 2mo ago|59 comments