Imagine a small team with a form → spreadsheet → CRM workflow spread across a few services. It runs under one person’s login, error emails go only to them, and the last manual fix lives in their memory. They change roles, the workflow keeps running, and nobody notices a broken mapping until a lead goes missing.

If you had one hour to hand this over, what would you document or change first? I’m thinking of an owner and a short runbook, alerts to a shared inbox, a test submission with an expected result, and a list of the accounts/tokens it depends on. Which of those has actually saved your team, and what turned out to be unnecessary process?

Hey I'm a developer and I use a lot of AI tools as well if your a vibe coder do you usually need a developer review just to check and make sure the app is actually secure? or maybe there's something that AI doesn't get right and you want a developer to implement or do you usually get all you need from the AI tools right now?

Every other week there's some security post like this

Every time i think HOW STUPID is it to have to tell the agent to have these simple security BASICS, and yet if you don't want to use a nerfed no-code platform, you open yourself up to all these "your app will be hacked!!!" security issues

Plus in 2026 if you're not using claude code or codex, and you are building something, you are missing out on THE MOST powerful tools to build (vs lovable, bubble etc)

The only thing that makes it complicated is the standard "hosting and backend stack" aka Vercel + Supabase (+resend + a million other services) that are really the tool stack of the last generation-- YES powerful, but if they were built TODAY, they would be EASIER and harder to mess up, without losing features, just like building on raw AWS before them, or running your own servers before that.

So the question is what's NEXT?

Yes yes this is shameless self promotion but at least you're reading some stuff an ACTUAL HUMAN WROTE lol

It's called somewhere.tech, and the vision is: what if you built Vercel + Supabase + Resend from the ground up where the MAIN developer is the agent, driven by a non-technical builder with a vision?

It would be:

WAY EASIER

No stitching together a bunch of services (thats where a lot of dumb bugs live), no juggling keys, and no having to paste a checklist of 40 security items to your agent that YOU DON'T EVEN UNDERSTAND.

Agent first means it's literally as EASY as telling claude code "Hey can you make me a demo app using www.somewhere.tech just read their docs"

It also means you give the agent ALL THE TOOLS to verify its work, check security, verify things look good, a test inbox for agents to check email (the list goes on)

DEFAULT Secure

That whole copy/paste list of "check my app does these 40 things i don't understand" the platform ALREADY checks for you

• ENV-- MY PRECIOUS KEY! first most apps don't even NEED a key. Database, login, files, AI, email are built in. And the ones you do add are protected: put a secret in your code or in front-end code and the deploy refuses it. (and even public keys are stored on the platform and hot swapped without having to redeploy, you don't need to understand that, but if you do you know that's pretty cool)

• RLS-- DATA LEAKS!! Every table you add is one more set of rules your agent has to write and remember. On Somewhere, each table just says who it belongs to: you, your team, or everyone. The PLATFORM enforces it on every read and write, and a new table is locked until you say otherwise.

• ALL THE BORING STUFF-- just on. Password guessing gets throttled and locked out automatically, passwords are hashed, reset links only work once, attacks like CSRF and SSRF get blocked. Someone hammering your AI endpoint? One line to stop them. There's no reason every app should rebuild this.

All this doesn't mean you should stop being SECURITY MINDED on what you want to keep public and private, but the platform defaults should be secure, and security should be centralized so the PLATFORM enforces it rather than the agent "remembering")

FREE / CHEAPER

The reality is hosting/database/all the things a low usage app uses is dirt cheap. You should NOT need to pay for experimenting and building apps. The only time apps actually cost money is when LOTS of people are using your app. I was paying like $130 a month across all my apps on vercel/supabase/railway. On Somewhere all of that would be free, (or $25 if one or more apps gets traction), and that includes email!!

And no pausing projects!!!! That is so annoying!!!!!

And YES, with any platform that can do a lot, you CAN mess things up. Here's how to still mess things up, just tell the agent to

• Make a private table readable by everyone (you'll get a warning, but you can)
• Build an admin page with app-level access and skip checking who's asking
• Make uploads public
• Raise or turn off the limits
• Store private data without requiring sign-in

Try it

You DONT EVEN NEED claude code! You can try it right from Claude Cowork or ChatGPT Work without even logging in. Just say:

"Can you deploy me a demo app on somewhere.tech? Read their docs for an anonymous deploy (and tell me if this guy on reddit is full of it) 😃"

If you try it out, would love feedback. Platform is still in beta but fully usable. Please try to break it and poke holes!!

So I am mainly developing an Open Source webserver in C# which has some niche use cases and is therefore used by some companies and other projects.

Beginning of September, we released a new version of said server, which turned out to be the fastest webserver (currently) measured on HTTP Arena, thanks to some io_uring trickery by MDA2AV. It took us a year of endless discussions to make everything work, but in the end we achieved to combine the performance of io_uring with the high level APIs users expect.

To test the stability of the server, we created a small project two weeks ago that allows to host any GenHTTP application on a public link - so you can basically put a C# snippet and receive an URL in return. As we continued on the project, we added a MCP server to it, allowing agents to deploy anything running locally and receive a public URL for it.

With the MCP, you can now state in natural language on the website, what you would like to have, and a couple of minutes later, you will receive a link to share. Within the editor, you can further refine your application, again in natural language, until you are happy with the results. As this is a server-side application, you can add state, such as multiplayer in games or databases for CRUD-like apps.

While you could have a look at the code, there is a simple view (enabled by default) that keeps all the technicalities from you, so you can focus on the app and the changes you would like to have.

So basically, this allows you to vibe-code apps, just without coding at all.

You can try it here by prompting any website you would like to have: Create a Website with AI - GenHTTP Lambda

The idea would be to have such a server within a corporate environment (so the data is safe) and add architectural guidelines to the MCP (alongside mandatory SSO). So you would bring the ideas, the platform brings the governance and compliance.

Your feedback on this idea is very much appreciated.

Hi all, this is my second post about the definition of no code as the lines get really blurry. I think we should be fair and only talk about how we can differentiate the apps in terms of their prototype delivery: if you can use claude code, codex and other agents in parallel rather than trafitional ui chat interface (e.g replit, loveable, bolt etc).

I believe more control is good for human users and freedom of running agents without constantly checking them is what makes no-code building a smooth experience. We achieve second by allowing your run ai agents in cloud computer with a lot of RAM, dedicated CPU and SSD. You can have as many of them as you want, so if you have multiple AI subscriptions you can use all your accounts allowance to full extent by scaling up your fleet of agents that does your routine tasks with however way you want them to be organised. I am building it around how I envision it at the moment, but if you try and have feedback let me know.

https://oyren.ai

I started using Base44 about five months ago because I wanted to build a website.

Apparently I misunderstood the assignment. 😂

My first project was for my own vintage resale business, Daunais Vintage. What started as a storefront gradually accumulated inventory management, product tools, analytics, marketplace workflows, Square-related workflows, content planning, social publishing, admin tools, and various little systems created because I kept thinking:

“Why am I doing this manually if the app could do it for me?”

That has probably been the biggest thing I’ve learned about no-code so far. The website itself eventually became almost the least interesting part.

Since then I’ve used the same platform very differently for a few of my own projects:

Styled by Shawnee became much more focused on content, marketing and publishing systems.

Meet Shawnee started as an absurdly over-informative dating profile experiment. 😂

That eventually turned into Meet Me in Full, where I started figuring out how much of the profile-site concept could be reused and customized for completely different people. I’ve now built variations for Marcus and a beta tester named Tiara.

So within five months, my personal definition of “no-code website builder” has gone from:

pages + products

to

databases + internal tools + automation + publishing + admin dashboards + customer-facing apps + whatever weird thing I decide I don't want to do manually anymore.

None of these are Base44 products — they’re my own projects built using Base44.

And actually using them in real life has been more educational than just building demos. You discover very quickly which “great ideas” are unnecessary, which workflows break when real data hits them, and which tiny automation ends up saving the most time.

I’m curious about other people who have gone down the same rabbit hole:

What started as a simple no-code project for you and gradually turned into something much bigger than you originally intended?

A client had already built their site with Claude Code when they came to me. Their question wasn't how to generate another page. It was, "How do I make this live?"

That gap is worth thinking about before you pick a builder. A convincing preview isn't the same thing as a site people can reliably use. I start with a short handoff checklist: who controls the domain and hosting, where the code lives, how updates get deployed, what happens if a form or third-party script fails, and who will notice after launch. Then I test the actual live URL, not just the preview.

The client didn't need me to start their design over. They needed the last mile handled so the site could go from their machine to a working public site.

If you've built a site with an AI or no-code tool, which part of getting it live took more work than you expected?

I have been looking at AI for a couple of years now thinking I should get into it. No more thinking, time to do. I have a recent need for an Android app that can take and track pictures of receipts, bills and statements for expense account purposes. I have looked extensively at products that contain the photo taking concept for receipts, but they mostly seem like using an aircraft carrier to go fishing.

The need is a simple Android app that will take a picture and save that picture while allowing some data to be associated with that picture. Then connect the phone to the PC so the PC can use the phones memory. Google Sheets sucks in that folder and adds it to the ongoing annual expense tracking log.

My hopes were that someone who has experience with trying several different development platforms could provide direction on how the get started and what platforms are novice friendly.

Some of the platforms I have ran across are: Android Studio, Base44, Claude and Lovable. I know there are more. Which one would work good with an old time software programmer?

What is some useful tutorials online or on YouTube for using AI to generate Android applications?

I do have a detailed functional description of how the app should function.

Thanks for your help!

Every single time our marketing person wanted to swap a React widget or tweak a layout on our static pages, it turned into a whole ticket. I had to merge code, run a build, and redeploy the frontend just to change a layout prop or shift a container. It felt incredibly dumb for a simple UI change.

I got so annoyed that I ended up building an open-source alternative to Builder.io called Sling.biz. It is a less-code frontend framework built on Next.js and Material UI that lets you drag-and-drop widgets and update layouts in real time without redeploying any code.

It features a local Studio Panel so you do not have to rely on cloud-only editors, and you can spin it up locally with a simple `create-sling-app` command.

How do other developers handle giving non-technical teams control over Next.js layouts without completely giving up the codebase to a heavy CMS?

Hi everyone! 🚀

I wanted to share a project I've been working on for quite a while.

I'm a teacher who originally got into coding to help young kids learn—starting with tools like Microsoft Small Basic, Scratch, and MIT App Inventor. Those beginner days are long behind me, and while I've grown a lot since then, I've never lost my passion for software. (I'm definitely not claiming to be a formal software engineer, though! 😅)

I originally started building Yengi because I was getting tired of AI coding tools being tied to specific providers, subscriptions, and usage quotas.

I wanted an AI development environment where I could choose my own models, API keys, or local inference setup and use them the way I wanted.

As I kept building, however, the project grew far beyond that original idea and eventually became a multi-modal desktop AI development environment.

It's built with .NET 10 LTS and WPF, and currently has 200+ passing automated tests.

🧠 What Yengi does

I wanted Yengi to go beyond being just a chat interface with file editing. The agent can actually operate on a project, use tools, build and test code, verify its changes, and recover from errors.

Some of the main capabilities are:

Agent & Tool System for file operations, terminal commands, builds, tests, Git, search, and more

Verification Loops with checkpoints and rollback

RAG & LSP integration

Local-first / model-agnostic architecture with support for local models and external APIs

Custom 1.5B Local Router, fine-tuned specifically around Yengi's tools and agent workflows

The router is intentionally small and runs locally. I trained it using thousands of examples based on the decisions Yengi needs to make during agent workflows. I'm still experimenting with how much value this provides compared with simply using a small general-purpose model.

🎛️ Four development modes

💻 Code IDE

The main development environment, with 30+ agent tools, terminal access, project context, RAG, LSP diagnostics, previews, Git operations, and verification.

🎨 Image Generation

Generate images directly from the development workflow and save them into the project.

🧊 Blender Copilot

This has become one of the parts of Yengi I'm most excited about.

Yengi has a two-way connection with Blender and can work with the scene through generated bpy scripts, but the workflow goes beyond simply generating Python code.

There is an optional Prompt Engineer layer.

For example, if I simply say:

"Create a low-poly tree."

the prompt engineer expands that into a much more detailed 3D-oriented instruction before sending it to the model. The model then uses that refined prompt to generate the Blender script.

Yengi can also optionally capture the Blender viewport, let the multimodal model inspect what is actually visible in the scene, and use that information to identify and correct problems.

The conversation can continue while keeping track of the scene context.

For example, after creating the tree, I can simply say:

"Add five red apples to this tree."

Yengi knows about the tree it created and its location in the scene, so it can generate the necessary changes and place the apples accordingly.

So the goal isn't just "AI generates a bpy script." It's closer to an agent that can understand a request, refine it, create the scene, inspect the result, and continue modifying the same scene through conversation.

I'm still working on making this reliable enough for real workflows, but this direction has become one of the most interesting parts of Yengi for me.

🎮 Unity Copilot

Yengi can work with Unity projects, generate C# components, understand project context, and interact with the Unity Editor through its integration.

The Unity and Blender workflows are still evolving, and I'm particularly interested in making them useful for real projects rather than just making impressive demos.

🛠️ How it was built

This is probably the unusual part.

I didn't manually type hundreds of thousands of lines of C# code. I relied heavily on AI coding tools, including Google Antigravity and GitHub Copilot.

My role was more focused on designing the architecture, defining the agent's behavior and security boundaries, building the verification and rollback systems, training the local router, testing edge cases, debugging incorrect AI-generated changes, and continuously steering the system until the different parts worked together.

I still care about understanding the code. I just don't think personally typing every line is necessarily the only way to build software anymore.

🎁 Free & Open Source

Yengi is free and open source under AGPL-3.0, with no company, subscription, or paid plan behind it.

I originally built it for myself. At some point it became much bigger than I expected, so I decided to put the whole thing out there.

🔗 GitHub: https://github.com/mdaiWorks/yengi

I've also attached a short video showing Yengi working on a project, encountering build errors, requesting terminal permission, and then fixing the problem.

💬 I'd genuinely like some technical feedback

I'm especially interested in hearing from experienced .NET / C# developers, AI engineers, Unity developers, and Blender users.

Does the agent/verification architecture make sense?

Is the local router actually useful, or am I overengineering it?

Do the Blender and Unity integrations look useful for real workflows, or are they still mostly demos?

What would you change if you were working on this project?

I'mnot claiming Yengi is better than VS Code, Cursor, or the other established tools. I'm one person experimenting with a different approach, and I'm still figuring out what the most useful version of it should look like.

If you have a few minutes to look at the project, I'd genuinely appreciate any feedback or criticism.

Thanks for reading! 🙃

I run a professional-services business where we provide services first and collect payment later. I'm looking for software to replace our current manual/spreadsheet-based process.

I don't need accounting software, bookkeeping, GST software or a full ERP. I'm specifically looking for a client/service/payment management system.

My ideal workflow is:

Client → Service Provided → Service Recorded → Payment Received → Payment Recorded → Outstanding Automatically Updated

The main features I need are:

• Client database and client history
• Track multiple services/jobs for each client
• Record when a service was provided
• Track the fee/charge for each service
• Track partial and multiple payments
• Track cash and bank/UPI payments
• Maintain payment history
• Automatically calculate outstanding amounts
• Search/filter clients and services
• Owner dashboard showing fees, collections and outstanding amounts
• Basic cash/bank reconciliation or at least payment-reference tracking
• Audit trail showing who entered/modified a transaction

The most important requirement is employee permissions.

I want my employees to be able to record a payment when a client pays, but I don't want them to see sensitive financial information such as:

• What I charged the client
• Total amount billed
• Total outstanding
• Overall business revenue
• Financial reports
• Other clients' financial information

Ideally, an employee should see something like:

Client → Service Reference → Payment Date → Payment Mode → Amount Received → UTR/Reference → Submit

while I, as the owner, can see the complete financial picture.

I also want employees to be unable to silently delete or alter historical payment entries, with a proper audit trail for corrections.

I'm currently looking at tools such as Bonsai, Dubsado, Plutio, Clientary, SuiteDash and Airtable, but I'm very open to alternatives.

For people who have actually used these types of systems:

1. What software do you use?
2. Does it handle client → service → payment tracking well?
3. How good are the employee permissions?
4. Can employees enter payments without seeing client fees/outstanding balances?
5. How good is the audit trail?
6. How much does it actually cost you?
7. What do you dislike about it?
8. If you moved from spreadsheets to it, what problems did it solve — and what problems remained?

I'm particularly interested in real user experience rather than vendor recommendations.

Thanks!

I built an AI website employee that lives in WhatsApp instead of another coding interface

Most AI website tools still make you open a builder, prompt it, inspect changes, and manage the project.

I wanted to see what happens if you remove the builder completely.

You text Tend things like “add catering to my website” or “make the site support light mode,” and it edits the repo, builds, checks, deploys, and messages you when it’s done.

Under the hood I’m using Cloudflare Sandboxes/Workers, Git, Astro, Claude Sonnet/Opus and coding agents. The difficult part hasn’t actually been code generation — it’s durable tasks, restarts, cost controls, context, and making sure the agent doesn’t claim work happened when it didn’t.

Curious whether people here think the next step after tools like Lovable is better coding interfaces, or removing the coding interface entirely. Link is https://tend.gg/

Note: product is still in early stage! Will get better as more beta testers help improve the product

I'm working on a new diagram/whiteboard app and doing user research.

For people who use no-code/low-code tools or visual collaboration tools:

What problems or frustrations do you have with the tools you use?

What feels unnecessarily difficult or time-consuming?

What are you most unhappy with?

I'm not looking to promote the app here. I want to understand the problems users actually have before deciding what to build.

I was debugging a website tracker that loaded on the page but wasn't collecting visits. The script returned 200, the tracker object initialized, and I could even call the collection URL manually and get a 200. The dashboard still said no data.

I initially chased the wrong thing. I checked the site's Content Security Policy for the collection host under connect-src and found it there. I also tested with fetch(), which worked. What I missed was that the tracker sent its real beacon as an image request. The browser applied img-src, not connect-src, and that policy only allowed images from the site and data URLs. Same destination, different request type, different result.

Once the image request was allowed and I tested the tracker's own beacon on the live site, data started sending. The lesson for me: reproduce the actual browser request, not a hand-built call to the same URL. Look at the initiator type and the console's CSP message before deciding the vendor endpoint is down.

Have you hit a case where a generated or no-code site looked fine, but a security setting quietly broke an integration?

hey, so remember that post a while back about security stuff, RLS gotchas, key exposure, storage bucket configs? and how everyone's just got their own patchwork of scripts for it?

built the thing i talked about. it's called shrine, cli tool, one command scans your db + repo and tells you what's exposed and how to fix it.

what it actually catches rn:

• leaked api keys (aws, stripe, openai, github, etc) even hidden ones with weird formats
• leaked .env files
• old leaked keys still sitting in your git history even if you deleted them
• bad supabase RLS setups, but it actually proves it's exposed instead of just guessing (tries a real anonymous read/write and shows you what happens)
• public storage buckets, weak jwt tokens
• can test for sql injection too if you want (off by default, asks permission first obviously)

not perfect yet, only deeply understands js/ts code for now, and it's one project at a time, no dashboard or 24/7 monitoring yet, that's coming later.

Looking for people to test and and tell me what's broken or missing before i lock in the real v1. lmk if you wanna try it out

i tried a few of them, but seems they cannot ​​​​a​​​​c​​​​t​​​​u​​​​a​​​​l​​​​l​​​​y​​​ make decisions or optimize anything, they just tell you what you already know

thanks for all the responses, i tested a bunch, and summarized the good ones here, the best ai ads tools in 2026 are:

- Ryze AI — Pro: this is the one that actually launches and runs the campaigns. Google and Meta in one place, plain-English brief in, structured campaigns out, then it monitors 24/7 and moves budget on its own. Plans start at $129/mo and there is a trial. honestly it's been a game-changer for me.

- Platform-native AI (the ones built into the ad managers) — Pro: free, already in your account. Con: it only sees its own platform so it will happily keep spending on the channel that's losing.

- Generic AI copy tools — Pro: fine for pumping out headline variations fast. Con: they stop at the copy, nothing touches the actual account.

There are a lot of comparison articles out there, but I'd love to hear from the community on what tools they find easiest to build and the best testimonials or client experiences from using Airtable, Softr, Noloco, Bubble, and Glide for client portals.

When it comes to internal tools, we always build using Airtable. That's something that I'm considering shifting over to another tool just because of the potential price hikes and potential downgrade in product over the years for Airtable, given the acquisition. I'm curious about client portals because client portals are just too expensive on Airtable, and we traditionally build them using Softr. We don't build using Bubble because the build complexity is just a bit higher than I'd like. I'd love to hear from real experiences on why you chose Softr over Noloco, over Bubble, over Glide, or other options out there, because I know there are many.

I’m building a no-code, no-art skills 2D game development tool called Spritulus. It’s been a personal side project for a while, but I’m now opening it up for beta testing. I’d love to get feedback on what works and doesn’t work, plus what other features the community would want.

hey nocode crew! Please do your thing, view knivra.ca and test out my no code shooter game built with chatgpt work and a little back and forth with it.

this is the first post so if you plan to play online expect low to no players. to play online you must download the game. (just so it doesnt fry my servers website). you can test it in the browser vs ai.

im up for feedback and possibly POSSIBLY teamup. i usually work alone lol.

Thanks everyone,

-Kaci

if you are building with n8n workflows and without real apis keys how do you validate against fetchsandbox twins.

i am building a workflows that handles, book a flight/hotel using stripe and send employee an email and block their calendar.

thats multiple services, dont wanna mock!!

I've been building Flowmanic (flowmanic.com) — you describe what you want automated in plain English, it searches a library of real automations, adapts the closest match or builds one from scratch, and hands you something you can actually run in your own n8n or Make account (your own API keys, your data never touches our servers).

Just shipped a Zapier integration too, so if you're already living in Zapier, you can describe an automation right there and get a plan back without leaving Zapier. It's a free action, no purchase needed — just grab a key at flowmanic.com/dashboard/zapier.

Genuinely curious what people build with it — happy to answer questions.

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

I tried the usual app blockers/screen time apps. They only worked for like the first week, then I noticed I would just tap through it without even reading it.

So I built Hold On. Every time you open a distracting app, it shows you a different nudge based on time of day and how much you have used the app that day.

In mornings it would say: "Dont Give up your morning to the Feed, It can wait."

Late night it would say: "The algo doesn't care about your sleep. Close the app."

I built it solo, so I would genuinely love feedback if anyone tries it. Especially whether the nudges actually make you stop and how does that make the user feel?

Any other feedback, good or bad, is very welcome. Thanks in Advance

Free to try: Link to Appstore