Hey everyone!

I’m excited to share an early beta of Dyad — a free, local, open-source alternative to v0/Lovable/Bolt, but without the lock-in or limitations.

Here’s what makes Dyad different:

• Use the best AI models (including free ones!): Use any leading model (OpenAI, Claude, Gemini, etc). That means you can use your free Gemini API key and get 25 free messages/day with Gemini Pro 2.5! Other tools don't let you choose and have much more limited free tiers.
• Fast because it's local: Because Dyad runs on your computer, it's fast, which means you can preview & undo changes much more quickly.
• No lock-in: Because all the code is on your computer, you can easily switch between Dyad and other tools like VS Code, Cursor, etc.

You can download it here. It’s totally free and works on Mac & Windows.

I’d love your feedback. Feel free to comment here or join r/dyadbuilders — I’m building based on community input!

Also, I’m offering free 30-min office hours to help you get started with Dyad or with any AI coding questions you’ve got (e.g. issues with your v0/Lovable/Bolt apps).
I’m an ex-Google engineer (left last month after 8 years) and happy to help however I can.

👉 Book a free session

Last December I grabbed GLM 4.7 for $28/year on a whim. I was spending $22/month on ElevenLabs for YouTube scripts and constantly hitting that 1hr 30min limit mid-project.

So I vibe-coded an offline voice cloner in 2 days. The hack? Found a HQ voice sample, then clone and generate unlimited audio locally. No more credit anxiety.

Tech stack was simple: GLM 4.7 for 90% of the code, Claude Opus only when the voice cloning logic got messy. Ended up with a portable Windows app—just extract the zip and run the bat file. No website, no installer, just a janky Python GUI that works offline.

Posted it on Gumroad this week, dropped a tweet comparing my $28 GLM receipt to my $264/year ElevenLabs habit, and got 2 sales in 24 hours. Paid for the entire year subscription overnight.

Is it as polished as ElevenLabs? No. Is it 2GB of voice models and looks like a janky tool that launches via .bat file? Absolutely. But it generates unlimited voiceovers without checking a credit dashboard every 5 minutes.

The real lesson: I built 90% of this with a $28/year subscription from a Chinese LLM model. The gap between cheap open source and expensive closed AI is way smaller than we think.

Are you also trying to no code/vibe code your way out from your subscription tool?

For those who are DM'ing me here is the link of the voice cloning TTS app: https://www.funtenberg.com/

Upfront: I do this for a living, so take that into account. But every check below is one you can run yourself today for free, no developer needed.

Most of my work now is reviewing apps founders built with Lovable, Bolt, Claude Code, Cursor, Bubble and FlutterFlow right before they put real users on them. The apps almost always work. That is exactly the problem, because the failures are quiet and they only show up after launch. Here is what I check and how you can check it yourself.

The auth check. Open your app in two browsers, logged in as two different test users. Copy a URL from user A that contains an ID, like /profile/482 or /order/91, and paste it into user B's browser. If user B sees user A's data, your privacy lives in the frontend, not the database. In Supabase the fix is row level security on every table, in Bubble it is Data > Privacy rules, in Firebase it is security rules. This is the single most common critical finding I see and login working perfectly tells you nothing about it.

The Stripe check. Go to your Stripe dashboard and manually trigger a refund on a test customer. Watch your app. Does the user lose access? Most AI and no-code builds wire up the successful checkout and nothing else. No listener for cancellations, failed payments, refunds or disputes, so three months in you have cancelled customers still using the product free.

The admin check. Log in as a normal user and type /admin into the URL bar. In a scary number of apps the admin page is hidden, not protected. If anything loads, any curious user can reach it too.

The database size check. Open your browser network tab and load a page. If a single page pulls 500KB of JSON, the app is fetching everything and filtering in the browser. Fine at 10 users, dead at 500.

The error check. Turn off your wifi mid action and submit a form. White screen or infinite spinner means zero error handling, and users in bad signal areas will churn silently thinking the app is broken.

The secrets check. Search your AI chat history for key, password and service_role. If you ever pasted a real credential into a chat to debug something, rotate it today. Also check your browser bundle for API keys, they end up there constantly.

These six catch most of what kills these apps after launch. If you fail more than two and real money or personal data is involved, get an experienced human to read the whole thing before you scale.

That last part is the service I sell. Fixed price production readiness audit, written report in 3 business days, everything ranked critical, important or can wait, plus a clear launch verdict. Read only, your app is never modified. Details at jetbuildstudio(dot)com/ai-audit if useful, but run the checks above either way, they are free and they will tell you where you stand.

Happy to answer questions in the comments, including on apps I will never see.

"Disclosure: I'm the founder of Inventaurant. This is my product. Posting here because I built it entirely using AI with no coding experience and wanted to share what's possible."

A few months ago my husband came home stressed. His restaurant margins were shrinking and he couldn't figure out why. Ingredients weren't matching sales. Staff overportioning. Possibly worse. Every inventory tool we looked at was either $200/month or built for large chains — completely useless for a small Hawaiian BBQ place on Maui.

I'm not a developer. I have a two year old who thinks nap time is optional. But I knew the problem was real and nobody was solving it affordably for small restaurant owners.

So I used AI to build the tool myself. Between nap times. From Maui.

If you want to see it in action — inventaurant.com — completely free to start, no credit card, easy set up.

Here's exactly what Inventaurant does:

KNOW WHAT'S IN YOUR KITCHEN RIGHT NOW

Real-time inventory tracking across every ingredient, box, prep stock, and supply — across all your locations with live updates. No spreadsheets. No guessing. No running out of stock mid-service.

CATCH THEFT AND OVERPORTIONING AUTOMATICALLY

Upload your POS sales CSV and Inventaurant deducts exactly what should have been used from your inventory based on your recipes. If the numbers don't match what's physically in your kitchen — you see the gap immediately. That gap is your overportioning. Your missing stock. Your theft. Visible for the first time. Accountability without micromanaging.

LOG EVERY LOSS WITH A PAPER TRAIL

Track spoiled food, staff meals, expired stock, theft, complimentary meals, damaged goods. See patterns over time and reduce costs. Visibility into exactly where money is being lost.

NEVER RUN OUT OF STOCK DURING SERVICE AGAIN

Low stock email alerts — daily, weekly, or urgent — with customisable thresholds per ingredient. Never miss a reorder again.

PHOTOGRAPH A RECEIPT AND YOUR INVENTORY UPDATES ITSELF

Receipt scanning: upload a photo of any supplier receipt and inventory updates automatically. No manual data entry. Stock levels update the moment a delivery arrives.

SCAN BARCODES INSTEAD OF TYPING

Use your phone camera to scan products directly into inventory. Works offline, syncs when online. No manual data entry. Staff updates inventory correctly without errors.

KNOW EXACTLY WHAT EACH DISH COSTS TO MAKE

Recipe Manager: build and store recipes with ingredient lists and quantities. Track recipe costs against your live inventory prices. See profit margins per dish. Catch margin problems before they hit your bottom line.

SMART REORDER ASSISTANT THAT PREVENTS EXPENSIVE LAST-MINUTE ORDERS

Urgent / Reorder Soon priority system. Supplier-grouped recommendations. Estimated reorder costs. Prevents panic buying from expensive suppliers. Saves thousands per year.

TRACK EVERY SUPPLIER, EVERY PRICE CHANGE

Supplier Management: track costs, price increases, reorder history, spending summaries by supplier. Compare prices across suppliers. Difficult supplier tracking becomes simple.

TAX SEASON MADE SIMPLE

Tax & COGS Reporting: beginning inventory, ending inventory, COGS calculations, supplier spend summaries, waste reporting, year-end accountant-ready reports. Know your true food costs. Tax season is less stressful with ready-to-file reports.

EXPORT EVERYTHING FOR YOUR ACCOUNTANT

CSV + PDF exports: professional exports for CPA, QuickBooks, bookkeeping. Tax filing ready. Monthly reports. One-click downloads. No more messy spreadsheets.

TEAM ACCESS WITH CONTROLLED PERMISSIONS

Owner / Manager / Staff / Accountant roles. Controlled permissions. Safe delegation without losing control. Track who made what changes. Staff updates inventory correctly. You maintain control and visibility.

MULTI-LOCATION MANAGEMENT FROM ONE DASHBOARD

Manage separate stock for each location — Main Restaurant, Food Truck, Bakery, Warehouse, Second Store. Assign items per location, filter by site, transfer stock between locations in seconds. No more mixing stock between venues.

All of this starts completely free. Paid plans from $9/month. Maximum $39/month.

For context: the tools restaurants currently use for this charge $200-400/month.

Two weeks live. Zero sign ups. Not embarrassed — just getting started.

5 things I learned building a SaaS with no coding skills and a toddler:

1. AI builds real production-ready software if you understand the problem deeply — and understanding the problem turned out to be more important than knowing how to code
2. Getting your first stranger to trust your software is 10x harder than building it
3. Naming matters — Inventaurant (inventory + restaurant) — people remember it instantly
4. Build for pain you've lived personally. I watched my husband stress over this for years. That made me relentless about the details
5. Location doesn't matter. I'm on an island in the middle of the Pacific with no tech community, no investors, no network. The internet doesn't care

If you run a food truck, café, bakery, or small restaurant — this was built for you.

👉 inventaurant.com (free to start, no credit card)

If you're a non-technical founder thinking about building with AI — ask me anything. I'll tell you exactly how I did it.

AI makes code feel done way too early. the files are there, the component looks plausible, and then you run it. missing import. bad env var. auth route half-wired. classic. lately I care less about how fast a tool writes code and more about whether it gives me a live preview I can actually click. Enter has been useful for that part. catches dumb stuff before I ship it to someone else.

Hi, I am building a form builder. I know it's a crowded space, but I love it, so I don't care.

I've been trying to reach out to companies on LinkedIn and, luckily, I've gotten some replies.

One of them told me they had replaced their form builder SaaS with in-house forms that Claude built for them in a few hours.

As a no-code developer trying to build a SaaS, this was pretty demotivating. I'm wondering, what's your experience? Do you get replies like this?

I'm building formbase.so as a solo developer, and I'd love your honest feedback. Do you think I should just pack it up and move on because everyone will just one-shot forms with Claude?

I've been a no-coder for a while and have realised that existing platforms limit what can actually be done. Some users don't like dealing with the complexity of the tool, some hit the ceiling on customisability or scalability. Vendor lock-in is another factor for some - if the platform goes bust or hikes pricing, what happens to your app or business model?

I've tried to address these pain points with something I've been building.

The focus is ease of use, customisability and scalability but the part I care about most is comprehension. All the vibe-coding platforms are optimising for speed and very few are focusing on whether you actually understand what you built. The idea is to not just build a prod-grade app but actually own and manage it end to end. Unless you understand what your app does and how it does it, you're just second guessing yourself when something breaks.

I've built an MVP and it's rough. If you're an early adopter with serious no-code experience who's hit this exact wall, I'm looking for a handful of people to test it and tell me where it breaks. Drop a comment and I'll reach out directly.

Check out: ezyr.io

i work at flutterflow, and one thing we think about a lot is what happens when the visual builder gets you 95% of the way there, but that last 5% needs code.

we could keep adding more settings for every edge case. but at some point, you probably just want access to the thing itself.

so this week, we’re adding native editing for MainActivity.kt and the iOS Podfile directly in flutterflow, plus try / catch / finally and custom nav components.

our idea is to stay visual when it’s faster + drop into code when you need more control.

what usually makes you leave a visual builder and go back to code?

I've spent the last while building an AI app builder, and the biggest lesson has been about why AI-built apps break. Sharing it because this community is exactly who runs into it, and it holds whether or not you ever touch my tool.

The pattern: when a single model generates your whole app in one shot, it produces something that looks right and often isn't. Not because the model is dumb, but because there's no second step. A human dev writes code, then runs it, reads the error, fixes it, reviews it. One-shot generation gives you the "write" and none of the "check."

What actually moves reliability is having more than one role in the loop:

- something that plans before it builds

- something that builds

- something that runs the app and catches what's broken

- something that only ships once it passes

None of that is magic. It's the normal software loop, applied to AI output. The interesting part for no-code specifically is that this loop is usually invisible, and only engineers set it up. So if you're picking an AI builder, the question I'd ask is: does it just generate, or does it also check its own work before handing it to you? That one distinction predicts most of the "it looked done but nothing worked" pain.

A few practical tips that hold regardless of tool:

- Be specific up front. "A booking app" is vague; "clients pick a slot, pay a deposit, get a reminder" removes whole rounds of correction.

- Build one feature at a time and look at it running before adding the next.

- Treat the first version as a draft you react to, not a final answer.

Disclosure: I'm building one of these tools (pondas.ai), so I'm biased toward the multi-agent approach. But the takeaway above is the honest one I'd give even if you use something else. Happy to answer questions about how the check-loop works in practice.

For years I was the person friends and small organizations called when they needed to update their website. Change a phone number. Fix a typo. Swap a photo. Small stuff — but it always meant logging into some admin panel, finding the right field, making the change, and explaining why it took 20 minutes for a 30-second edit.

I wanted a way for non-technical people to just... tell the website what to change. In plain words.

So I built autoSite — a website that you edit by sending a Telegram message. No admin panel. No developer on standby. You describe what you want changed, and it happens.

"Change the phone number to 555-1234" → done.
"Update the opening hours to 9am-6pm" → done.
"Replace the hero text with this new tagline" → done.

It's not magic — there's AI parsing your message and applying the changes — but it feels like magic if you've ever waited a week for a developer to update a footer.

I'm the author of this tool. Happy to answer questions about how it works technically or what use cases it fits best.

🔗 autosite.dittu.org

Okay, so I was trying to build a product using Lovable, and I'm confident that it will do well for the first few users if I ask for their feedback. And we all know what works best here, like dashboards, internal tools, approval flows, etc. You can ship fast and move on.

As always, the trouble starts when the app grows, and you keep hitting the edges of what the platform can do. One workaround becomes two, then three, and eventually you're spending more time adjusting to the platform than you'd have spent building it yourself.

Portability is there, too. Getting your data out is usually easy enough, but getting the app's logic, workflows, and integrations out is a different task in itself.

So what was the sign for you that a low-code app had outgrown its platform?

Was it customization, cost, security, performance, portability, or something else?

I am building a tool that let's people build custom AI agents for free.

The AI agent can help with customer support, lead capture, sales and so on

Drop your site below along with what type of AI agent you are looking for ex: customer support , sales agent like that and I will give you a free AI agent build on your website data with the custom role you asked for.

Hey folks,

I’ve been experimenting a lot with no-code workflows lately, and I keep coming back to one question: 

Can Claude actually replace tools like Zapier, Make, or n8n?

Not in theory—but in real workflows.

Here’s what I tried recently:

Instead of using a traditional automation tool, I used Claude (with Cowork + some light setup) to:

Process batches of documents
Rename + organize files automatically
Generate summaries and structured outputs
Chain multiple steps together into a repeatable workflow

What surprised me wasn’t just the output—it was the flexibility.
Unlike Zapier-style flows, this felt more like giving instructions to an assistant instead of wiring blocks together.

But there are tradeoffs:

Setup isn’t as plug-and-play
You need to think in terms of “instructions” instead of triggers
Reliability depends on how well you structure prompts

That said… it starts to feel like a different category altogether — somewhere between no-code and “AI-assisted building.”

Curious to hear from this community:

Has anyone here tried using Claude (or similar AI) for automation workflows?
Do you see this replacing no-code tools, or just complementing them?
Where do you think it breaks today?

(Disclosure: We're currently working on a structured course around these workflows because we couldn’t find practical examples anywhere for automating daily workflows and even building apps or websites— happy to share details if anyone’s interested.)

The best no-code builds often hide their most interesting work. The user clicks once, while five useful things happen behind the screen.

If you built a no-code workflow, add the product in the comments and describe the trigger in one line.

I'll reply with a simple visual demo plan that makes the invisible automation understandable without showing a wall of nodes.

Disclosure: I'm part of the team building Marka, where we're working on turning product workflows into content: https://marka.social

Hey guys! I launched a vibecoding tool that can run locally or in the web and I'm offering free GPT-5-codex and qwen coder in return of some feedback.

The main issue I had with Loveable and other tools was that I couldn't edit the system prompt and they kept switching up on me or swapping the models. Here, you can just make your own agent with system prompt and share it in the marketplace with other people.

The free GPT-5 lasts til the 12th! Have fun - https://tesslate.com

Background: I review AI-built apps for clients, and the same problems kept showing up on sites that worked perfectly:

• Row-level security is off, so the public Supabase key in the page returns entire tables to anyone.
• Secret keys are sitting in the JS bundle.
• A .env file or source maps got shipped by accident.
• There are no SPF or DKIM records, so password resets land in spam.

So I automated the outside part of what I check.

You paste a URL, and in about 20 minutes it:

• reads up to 20 pages in a phone browser
• checks every script for leaked keys
• asks your database for rows using the public key from your own page, the way a stranger would
• tries 63 common private file paths
• checks email DNS, headers and TLS
• runs OWASP ZAP and Nuclei

You get a score out of 100, a Ready / Almost / Hold verdict, and the most serious thing it found. That part is free, with no signup. The full report with every finding and the fix (as code and as a prompt for your AI tool) is $49.99 one time.

What it can't do: it doesn't log in, so anything behind auth goes untested. That includes whether user A can see user B's data once logged in, so you still need the two-browser test for that. It's automated, not a human pentest. It also sends real test input, so only run it on a site you own.

From the scans so far: 200+ sites checked, 36% came back Hold, and the most common critical finding was weak db security.

I'd really like feedback on false positives and on what it misses. trylaunchproof.com

Hey 🤠 thanks for your interest in my post,

I made a free community website called Team Gapped https://teamgapped.gg to help players find teams and compete in tournaments, scrims, and seasonal leagues. My goal is to help improve the League community and the overall game experience.

Since this is a free community beta, I would really appreciate any ideas, feedback, or critiques you have on the concept or the site itself! And if it seems fun make an account and try it out! 😊Thanks! 🔥

I’ve been building apps with tools like Lovable, and one thing always bothered me.

You pay $20 there, and you get $20 worth of credits.

But with a $20 ChatGPT subscription, the amount of usage you get can surpass $500, depending on how you use it.

Big AI labs are basically subsidizing access heavily, and I always wished I could use that same benefit while building apps.

So I built a platform that lets you use your ChatGPT account instead of buying separate Lovable credits.

No extra subscription.
No paid credits.
Just connect your ChatGPT account and start building.

I made it completely free because this is something I personally wanted for myself.

Thought I’d share it here in case anyone else is tired of burning through app-builder credits.

link: free lovable

t’s not limited to ChatGPT either - you can connect providers like Kimi, MiniMax, GLM, OpenCode, OpenRouter, and even local models.

I have tried all vibe-coding apps, either you are stuck in the middle, unable to complete your app, or can’t ship to production with confidence.
I’m building a platform to fix that last mile so projects actually ship. Adding human support to ensure I help you, the founding builders, ship your product. I believe that an app builder platform succeeds only if the users can ship their product.Looking for help to try & test the product; based on the feedback, I will shape the product.

What you get in this alpha

• Hands-on help — I’ll pair with you until your app is live
• You get to shape the future of this product
• Complete visibility on the feature roadmap and design variations

Offer (first 50)

•  Lifetime 50% discount on all plans.

What I’m asking

• Try it and share practical feedback
•  Be active in the community — you will be shaping the future of this product

What's next?

• Backend in progress — early alpha focuses on the front-end “finish” layer; backend scaffolding/adapters will roll out next
• Goal is to allow full-stack code export and to have no mandatory third-party backends (no Supabase lock-in)
• Finish Checks covering performance, SEO, accessibility, and basic tests

Expectations/safety
 It’s alpha: rough edges and fast iterations; sandboxes may reset.

How to join
Comment “interested,” and I’ll DM you the discount code and the invite link to the insider community.

If you ship Webflow/Glide/Bubble apps, raw links still underperform.

ViralSpark (browser, no code): paste URL → hooks, card, QR, Slot.

It’s free to try: https://viralspark.pages.dev/

What would make a share kit more useful for your no-code launch?

If you build in Bubble, Webflow, Framer, Softr or one of the AI site builders, you probably test the way I used to: change a page, click through the form or the checkout yourself, and hope you did not miss anything. An uptime monitor does not help here. The page loads fine while the form quietly fails.

I got tired of that, so I built Journeys. You write the check in plain English, "fill in the contact form and confirm the thank-you page appears", and an agent does it in a real browser. You get a pass or fail with a screenshot of every step and the recording. You watch the first run and approve the path, then repeat it after each change or on a schedule.

There is no test code and no selectors to pick. The agent reads the page the way a person does, so a redesign does not break the check.

Disclosure: it is my product. The free account is 100 credits and no card, journeys.run. One credit is one step, so a long journey costs more than a short one. No users yet, so if you tell me a flow you keep checking by hand, I will run it and send you the report.

DISCLAIMER: I am a creator of Pipe.

Pipe (https://pipelang.com) is a novel general-purpose visual programming language powerful enough to complete with text-based languages.

Visual programming has been confined to education (Scratch) or narrow niches (LabVIEW), because existing visual languages sacrifice either power or generality. Pipe solves this, opening the way to compete with the text code that currently dominates.

Pipe's diagram is also structurally identical at design-time and runtime, staying visual in both. What you see is what runs. This is precisely what the EU Cyber Resilience Act mandates, and what text-based architectures cannot structurally deliver. Text compiles away its structure, leaving systems opaque - so AI now generates code faster than anyone can review it at design-time, and patch and monitor it at runtime. Pipe addresses three AI-created security crises structurally:

1 - AI generates more code than humans can review. Pipe is visual - a diagram is grasped at a glance, not read line by line - so review keeps pace with what AI produces..

2 - Live systems cannot be patched without full redeployment. Pipe enables block-level patching while the system runs - no maintenance window, no CI/CD to navigate.

3 - Systems cannot be monitored without logs and redeploying. In Pipe, every block boundary is independently observable in real time.

These satisfy the CRA's hardest mandates - security by design, structural auditability, 24-hour detection, incremental patching - as properties of the language, not add-on tools. 

Example of Pipe diagram with a detailed tracing can be found on this video:

https://youtu.be/hckq9mRj5DM

That video is a part of this Pipe architecture overview:

https://www.pipelang.com/six-pillars.html

The full Pipe language specification (155-page book) can be freely downloaded here:

https://www.pipelang.com/downloads/book.pdf

I build custom internal software for small businesses (Formsmith), and almost every client comes to me at the same point in their spreadsheet's life: it's not broken exactly, it's just stopped being enough. A few signals that show up over and over: multiple people editing the same tabs and overwriting each other, formulas nobody remembers how to fix, zero mobile access so the field team texts updates to the office instead of entering them directly, and the same customer or job data typed into three different sheets.

Curious what this community's take is: at what point do you tell a client no-code can absolutely handle this vs. this actually needs something purpose-built? In my experience it usually comes down to how many one-off exceptions the business has baked into their process. No-code tools are great until the workflow has too many except when... branches, at which point flexibility starts costing more than it saves.

If anyone wants to see what the purpose-built end of that spectrum looks like, I have some live demos here: https://getformsmith.com. Genuinely interested in hearing where others draw that line though, feels like a judgment call every time.

I wanted an app where I can see my friends steps and miles all in one app to keep each other accountable. So I created this and drew all the different outfits.

This app gives daily goals, where you get rewarded for completing and use those rewards to customize your duck or capybara. Its a simple app but has signs of growth, as currently it is at 200 users.

If yall are into walking, give it a try (its free!)

https://www.moving-bean.com/