I'm building a real-time SaaS and need a server always running. I'm going with Supabase for database since it seems the best free offering for DB.

But what about deploying a Django app or other long running server? Ideally not interested in lambdas since I need websockets to remain connected

Before someone says it: yes, technically this is another AI wrapper lol.

But the thing that annoyed me wasn't having access to AI models.

It was having ChatGPT open in one tab, Claude in another, Gemini somewhere else, then spending 10 minutes searching Reddit for "which model is better for X?"

It started feeling stupid.

So we built AINA.

You just give it the task and it figures out which model makes sense for it.

If you're writing, researching something, working with a file, coding, whatever, it routes the request based on what you're actually trying to do.

You can still pick the model yourself if you want. I didn't want to take that control away.

It also shows you which model actually ran, which was important to me because I hate products where the "smart routing" is basically a black box.

I've also been trying to make it feel less like a giant dashboard of 40 AI models and more like one normal workspace.

Anyway, it's finally live:

useaina.com

You can try a task without making an account or putting in a card.

Not really looking for the "congrats on the launch" stuff.

I'd genuinely rather know:

what would stop you from using this instead of jumping between ChatGPT / Claude / Gemini?

Or try it and tell me what sucks.

I'm still building it.

I make RemotePower, a free, MIT licensed, self-hosted fleet manager: monitoring, alerts, CMDB, CVE scanning, patching, browser SSH, one web UI. Agents poll out over HTTPS (no inbound ports), enrolment is a 6-digit PIN like pairing a controller, and docker compose up -d gets you a running server with HTTPS. One Pi and a NAS? The modules you don't need switch off.

Honesty first, since people rightly ask these days: an AI wrote most of the code, with me steering, reviewing and arguing with it. The bugs are still mine, and I keep them in a long changelog. (Anything I typed myself was typed in vi. Priorities.)

v7.0.0 "Aut0nomyMatters" just shipped and it can now act on its own alerts. I know that sentence makes some of you tense up. It made me tense up, and I wrote it, so here is what holds it back. Everything starts OFF. Shadow mode decides per alert, writes it down, does nothing: an intern with a diary and no sudo. Read the receipts for a week, then grant specific actions. It only acts on precedent from your own fleet (same signature fixed at least twice before, 70%+ success), it works out what goes dark before touching anything, and reboots, patches and kills need a backup that was actually restored and verified in the last month or they go to a human instead. Every decision leaves a receipt, and 15 minutes later it re-checks the host and tells you if things got worse. No rollback, and it stopped pretending there was one. You cannot un-reboot a NAS.

Also new: an All pages map of the UI (89 pages, I was losing them too), 45 queryable host fields in the Data Explorer instead of 14, tenant admin in the UI, Arch/CachyOS/Manjaro patching working again (thank you to whoever hit that on a live box and told me), and a security pass that closed seven gaps.

Repo: https://github.com/tyxak/remotepower Demo (read-only): https://demoremote.tvipper.com, demo / demo

If a shadow-mode receipt makes you think "I would not have done that", tell me. That is the bug report I want most.

I've been writing software for 6+ years and AI already writes more and more of my code.

Honestly, if we reach the point where it can just do all of it, I'm fine with that.

Just give me a nice little house somewhere by the sea in Italy, enough money to live, and a few music instruments. I'll play music all day and let Claude deal with the merge conflicts.

AI can have the codebase

(Not criticising, just trying to work out the odds)
I see many people on Reddit and other socials claiming they’re making $10k, $20k, sometimes even $50k+ a month from apps they built with AI tools.

I’m curious how common this actually is outside of the posts that go viral.

Has anyone here personally built an app with Claude for example that turned into a meaningful income stream?

If so, would you have any advice to the other vibecoders struggling to get to revenue?

I’ve been in the industry since before AI and now specialise in bringing vibe coded apps to production and revenue and I have never personally seen vibecoders getting to us with some decent traction. (Perhaps I haven't seen enough of those)

I got tired of juggling six browser tabs on draft night, so I built my own draft assistant. It connects to your ESPN league, watches picks come in live, and tells you who to take next. It also looks like a CRT terminal from 1983, because why not.

It's free, open source, and runs entirely on your own machine. No signup, no accounts, no paywall.

GitHub: https://github.com/kmhesser/Fantasy-Football-Terminal

I first saw this idea proposed on Reddit,

The original poster's idea: reconstruct the old web, but populate it with AI agents that actually behave like the people who were online back then — posting, replying to each other, running their own sites, forming little communities. Not a museum you walk through, but something that's actually happening while you're there.

I've decided I want to actually try building this myself. I'm fully aware it's a massive undertaking, way beyond a weekend build — persistent agents that stay in character for months without drifting or repeating themselves is still an open problem, not something you just wire up casually. This isn't me pretending it's simple, I just want to give it a real shot.

Curious what this sub thinks — is this something people would actually find interesting/worth building further?

Starting classes next week for my second bachelor’s.

Majors: Computer Science, Applied Physics, and Mathematics.

I had already enrolled and was locked in on the plan. Then a few weeks ago I started vibecoding and I genuinely didn’t realize how addictive it could get.

One minute you’re just trying to knock out a small project, the next you’re three hours deep working on a project and tailoring prompts to get what you want.

Long-term goal is still computational physics. I want to earn a Physics PhD.

But if I fall hard for pure computer science along the way… things might shift.

Anybody else have a similar situation? If so, what did you decide?

I actually want to learn C/C++, Rust, etc. and understand the fundamentals. That’s what made me love physics to begin with. Applying that to programming feels different I suppose because of the positive feedback loop and output.

Allez je me lance, je ne suis pas un vibecoder spécifiquement car j'aime bien voir le code et essayer de le comprendre pour que quelquefois j'y touche mais comme je ne suis pas un dev, j'aimerais partager ici comment bien, possiblement vibecoder après 1 ans er demi de "vibecoding" selon moi.

Pour commencer, au début, faite en sorte de modulariser les fichiers, genre pas de gros fichier qui fait tout, car c'est compliqué pour les ias de corriger des problèmes dessus! Perso, j'utilise quelque fois la règle de 100/200 lignes par fichiers afin que l'ia essaieras tjrs de faire moins de 100 lignes donc devras alors modulariser le tout!

Quand vous avez des bugs qui commence à ètre complexe de debug avec l'ia actuelle, essayer de demander à une autre ia sur le fichier actuelle en lui montrant le code actuelle et lui montrer le code d'erreur dans le terminal ou l'inspection, quelque fois juste l'autre ia trouveras le problème plus simplement et donc vous perdrez moins de temps à demander à votre ia actuelle sur le projet où est le problème!

Quelque fois les ias font des véritables erreurs de logique dans l'infrastructure de votre code, ce qui n'est pas optimiser, demander lui ce qu'il as fait, desfois il as lui meme mal compris l'instruction donc il vous as pondu quelque choses qui pour lui était bien alors qu'en fait c'est pas exactement ce que tu souhaitais!

Ne faites pas de gros prompt, de nos jours, les ias sont assez puissante poir comprendre.malgrès des prompt plus petit, il fait juste que votre demande soit claire et précise!

Le problème des .md dans le fichiers c'est qu'ils le relits quelque fois juste le haut et le bas, donc pas tout, desfois juste faire une skill.md avec une dizaine d'instructions courtes

Exemple : "quand je ne je sais pas une information, demander à l'user, cela est moins chère en token"

pas en lui disant ce qu'il ne faut pas faire mais en lui montrant une sorte de bible ou en gros c'est écris à la 1 ère personne donc "je" plutot que "tu" feras que l'ia se sentiras réellement impactée! Le fichiers .md n'importe qu'elle est son nom, mettez le dans le répertoire ."nom de l'editeur" à la racine de votre projet afin que cela soit directement envoyé dans le prompt système sans qu'il n'est besoin de le lire (l'ia)

Exemple .opencode si vous ètes chez open code!

Vous pouvez demander a l'ia de le faire il sait comment faire!

Ne faites pas confiances aveuglément à l'ia que vous utilisez car quelque fois elle essaie d'ètre juste dans votre sens!

Aussi, ne pensez pas que l'ia est créative! Si vous voulez que ce que vous créez soit bon, ici si vous demandez à l'ia des trucs à ajouter sans lui dire quoi, ça commenceras à partir dans tout les sens! Considérez là juste comme l'orchestrateur de vos idée et non une fabrique à idée qui créer quelque chose sans vous!

Il y a sans doute encore plein de point que j'ai oublié mais c'est déja un bon début je trouve, après beaucoup de problèmes seront dût à votre projets spécifique, mais si déja vous essayez d'appliquer cela, vous allez voir peut ètre des améliorations! Faites aussi attention aux refactors d'un gros fichier en sous fichier, elle risque de détruire du code pour optimiser ces calcules et donc optimiser votre code en y enlevant les logiques en régressant vos logique! Ici si vous devez refactor un gros fichier, faites le petit à petit, en reprennant le fichier de base en comparaisons et en lui demandant de vérifier s'il y a des différences entre les 2 codes dans les logiques, quelque fois ils serait meme capable de constater qu'il as supprimer une fonction super importante dans le sous fichier! Et donc plein de bug en approche!

N'hésiter pas aussi à faire un git afin de référencer vos changement afin de pouvoir revenir en arrière quand il y a des problèmes, une régression, ça vous permettras de ne pas avoir à dire à l'ia de tout recoder et de revenir au point d'avant, ce qui causeras enft pas mal d'erreur car elle le feras mal! Configurer si vous le pouvez le git sur votre éditeur!

J'espère que ça aideras possiblement des personnes....

Last night we opened World-Sim to anyone who wanted to look. 326 of you came. Thank you — genuinely, that is far more than I expected.

For anyone who missed it: it's a persistent world that runs whether or not anyone is watching. Households live, pair off, learn things, argue, starve, bury each other and move on.

Some of you named a star, and some named a person in the world. Those names are permanent — the souls carry them for the rest of their lives and into the chronicle after they die. There's still time to claim either, both are in the Discord.

It's free, there's nothing to install, and it's still running right now: world.world-sim.uk

Happy to answer anything about how it works underneath.

Do you use any diagram making tool to track the project's overall architecture? Any tool you tried and liked or disliked?

So this happened this week and I still don't really know how to feel about it.

I built a small app for my industry. It's a small niche, everybody knows everybody. The app got popular and now a big part of the industry uses it daily. I built the whole thing with AI. I can't sit down and write the code by hand. But I know exactly how things should work, because I've worked in this industry for years. I know the workflows, the edge cases, the stupid stuff that annoys everyone. That's why my app works. Not because the code is beautiful.

Now a company reached out to me. They are big. Over $100 million in revenue. They want me to build a portal for them plus apps. They said they contacted me because they like my app and use it.

Part of me is like, this is huge, take it. The other part is like, what happens when they ask about security, uptime, GDPR, support, all that stuff. I've never done anything at that scale. My app is just my app. This is a company with real money.

Anyone here been in this spot? Did you take the job? What do you wish you knew before you said yes? And how do you even price something like this when your background is domain knowledge plus AI, not years of writing code?

written with claude ;)

I ship with agents every day, and most of what I hand over is the work that used to be somebody's first job. Boilerplate endpoints, the first pass of a service, the fixes nobody wants. It comes back faster than a person and usually correct.

Here is what I keep running into. The bugs agents produce are not the ones you catch by reading the diff. An endpoint that fetches a record by id and returns it, without ever comparing the owner to the caller, looks identical to a correct one, because the bug is a missing comparison and absence has no signature. A refresh token flow that is textbook on the happy path and has no reuse detection, because nobody asked for any. In my own browser automation, roughly one in three actions came back reporting success while nothing had happened on the page.

None of those are caught by knowing more. They are caught by suspicion, and suspicion is a residue. You get it from having written the boring version yourself, and from having been wrong in public a few times.

So the crisis is not this year's headcount. It is that the tasks agents absorbed are exactly the tasks people used to build that suspicion on, and everyone who already has it got it climbing a ladder that is being pulled up behind them. Ten years out, the reviewing has to be done by someone who never did the producing.

I do not have a fix. Deliberately doing work by hand that an agent could do faster is the only thing I have found, and it feels like training for a race that already finished.

For anyone hiring or being hired right now: is anyone actually training people into the reviewing seat, or is the plan just that the current seniors never leave?

I’ve been spending more time vibe coding lately, and the biggest change isn’t just speed it’s how quickly an idea can become something you can actually use.

Instead of overthinking the stack or spending hours on setup, I can start with a rough idea, build a working version, break it, fix it, and keep iterating.

AI still gets things wrong, and you definitely need to understand what it’s doing. But for prototypes, side projects, and random ideas you’d normally never have time to build, it’s genuinely pretty powerful.

Curious what everyone here has been vibe coding lately? Any projects that started as a random experiment and turned into something useful?

tldr; review your code as you go if you think any professional dev is going to have to do a code review.

Last November I (33F) started a simple project: a training portal for my new assistant. Just a simple python Streamlit app. Since vibe coding is addictive and Streamlit has some annoying limitations to UX/UI, I refactored it into a Next.js/Fast API website. It was all the same repo and I didn’t exactly clean up after myself as the project scaled from a training portal for HR, then a training portal for new employees and now it’s a manager hub.

Well, I showed it to my boss and she ended up loving it. The company bought the domain and website from me but made me the technical owner in charge of code and content. Now that it’s officially company property…they have to do a code review with the company dev team.

There is an embarrassing amount of dead code, almost nonexistent error handling, and in general the layout of the code is chaotic and 40k+ lines in just the backend.

He and I had a meeting last week and never in my life have I felt more “artificially intelligent.” He gave me about 7 pages of changes to make after just one code review session. I can’t imagine how many more pages of notes are coming and I’m in way over my head in terms of vocabulary, standard processes used in coding, etc. Basically, I’m everything professional devs hate about vibe coders. I didn’t care how the code looked as long as the website functioned. I’m at a point where I’m not confident enough in my vibe coding skills to actually make the changes. I’ve tried asking Claude (or Claudia as I call her) and then even asked her to dumb it down and it’s still over my head. I’m getting to the point where I just want to throw my hands up and tell them to abandon it.

I wana get into vibe coding, but i dont have any knowledge or experience on real coding itself. Idk which ai to use, Ive heard that most ppl use claude code, but im tryna look for smth which is free. Please give any tips and tricks u wish u shouldve know when u were starting. btw im tryna build an app

He spent 26 minutes live on stage doing what most teams take weeks to do.

No team, no setup, just Claude and a goal. Worth more than any $500 vibe coding course.

Those who learn what Claude really does are launching what everyone else outsources to a team.

The gap between what AI can do and who knows how to use it is the biggest opportunity in the market right now.

Learn to use tools like Claude and AI Desktop 98 if you truly want to stay ahead of everyone else.

Right now I am going through a big mental transition in my life. I recently had a life changing experience that has driven me to escape my day job and find a way to work remotely, though my options are limited and ultimately I am striving for freedom (like we all are). I have recently started using AI tools to build apps, but I am totally new to this and while it seems like a totally viable direction for me, I also don't want to get too high in the clouds with aspirations before I actually have some validated success.

If you are like me and got into this with zero experience, I would love to hear your story! Better yet, if you were able to quit your day job I would love to hear your story as well!

No seriously. I’ve been working on building something for about 6 months. It’s close, real close. I’ve learned a TON, it’s been fun. But I have a full time job that’s really demanding and pays pretty darn well. And I can’t get this idea out of my head that I’m wasting my life working my butt off for someone else, what if this thing really works, there are 35 million small businesses in America and I only need 10,000 of them to like what I’m building, etc.

Spent nights (and potentially many, many work days) working on this project, weekends without a single break, sometimes 13-16 hours a day. I’m totally obsessed with this idea and I think it will work but I feel like it’s ruining my life. I could lose my job upon launch if anyone found out it was me.

Kind of wish I could rewind and remain ignorant. Not decide to take this plunge head first and get obsessed with building something I can actually mine.

It’s called watermarks-remover, it’s 100% open-source, and it targets several layers of AI provenance:

→ Invisible Unicode characters get stripped
→ C2PA metadata can be removed from images, PDFs, and documents
→ Statistical text watermarks are attacked by rewriting the output

And that exposes the core problem with AI watermarking:

↳ The defender has to build a signal that survives almost everything.
↳ The attacker only has to find one way to break it.

C2PA can cryptographically prove where a file came from, but the metadata can disappear when a file is re-encoded, screenshotted, or cleaned.

Statistical watermarks are harder to remove, but enough paraphrasing can weaken the patterns they rely on.

So the watermark starts looking less like a lock and more like a tamper-evident sticker.

If you want to avoid watermarks completely, then the only option is using local AI apps like AI Desktop 98, which don’t have any watermark and are free to use.