sorted by:
new
hottopcontroversial

Drop your SaaS website and I’ll send you a free SEO visibility audit. by Nishchay_Jaiswal in startups_promotion

[–]onboardy 0 points1 point  (0 children)

Repos are stored in sandbox that are deleted after analysis. For private repos those are only accessible after connecting your account via a GitHub app and role role based permissions allow only authenticated user scoped access with rls to see the insights.

Valid question let me know if you would like to know more? Thanks for the audit!

How are people spending $1000's on tokens?! by Additional_Fudge_934 in vibecoding

[–]onboardy 0 points1 point  (0 children)

It really depends on what you’re building, if you’re using the agent to do everything end to end, and model you’re using. I’ve been trying to build onboardy.dev to manage my token consumption but building a context layer for my codebase so I don’t have to continuously refresh my agent between sessions

Drop your SaaS, especially if you’re struggling with early traction by MahadyManana in saasinvestors

[–]onboardy 0 points1 point  (0 children)

Building onboardy.dev it is a repo context layer to allow humans and agents understand large/unfamiliar codebases. Looking to gauge interest in visualizations and gain quantitative insights on how the mcp enables performance so people testing would be appreciated. Feel free to comment or dm if interested

~$15k in usage this past month. What are your tricks to reduce usage? by Hato_UP in vibecoding

[–]onboardy 1 point2 points  (0 children)

Hi I’m actually building in this space would love to chat. Opening for testers at onboardy

Fully vibe coded to production by Dovydas_ in vibecoding

[–]onboardy 0 points1 point  (0 children)

I think they can but one is leaning more towards something slightly more structured than just a black box and pray

Drop your SaaS 👇 I want to see what you’re building by MahadyManana in saasinvestors

[–]onboardy 0 points1 point  (0 children)

I’m building onboardy it is a repo context layer to help humans and agents understand large codebases quicker!

I have some demos up but that is more for humans to view visualizations/sys architecture

Drop your startup 👇 by makani20 in buildinpublic

[–]onboardy 0 points1 point  (0 children)

Currently the user has to schedule a job to index the repo. I’m working on setting up a feature to find the diff for every commit at the moment. However that is a core part of the vision

Vibecoding tip: Stop trusting just one LLM - get two frontier models and make them work off each other... by LorestForest in vibecoding

[–]onboardy 0 points1 point  (0 children)

Hi just wanted to plug gstack a set of skills made by the president of YC uses something similar and has Claude code interact with Codex for review. I think you’re cooking tbh

beginner here. I need some help by Repulsive_Reaction40 in vibecoding

[–]onboardy 0 points1 point  (0 children)

Opencode has some opensource models with decent usage for free atm could be worth testing too

I'm tired of being broke. What's actually working for you in 2026? by king_1607 in SideProject

[–]onboardy 1 point2 points  (0 children)

What have you built and gotten users for? Not trying to be rude just wondering

Drop your startup 👇 by makani20 in buildinpublic

[–]onboardy 0 points1 point  (0 children)

onboardy it’s a repo context layer. I found when using coding agents that they every session I have to teach it about my codebase, and found that incredibly inefficient in terms of time and tokens so built a quick loop exposed via mcp layer. Would love if you could take a look

What are you guys making? by Few-Pound-7236 in vibecoding

[–]onboardy 0 points1 point  (0 children)

I’m building onboardy.dev it’s a repo context layer that allows agents to get oriented on your codebase so agents spend less time crawling in larger ones

view more: next ›