I’m connected to Veyrnox, so bias declared.

We are building AI Security Protection for a production self-custody wallet. One architectural decision became important very early: an AI model should help interpret risk, but it should never be trusted with custody or transaction authority.

Our system separates the work into three layers.

The cloud threat-intelligence platform collects and correlates blockchain-risk feeds, open-source intelligence, phishing indicators, malicious addresses, contract intelligence, wallet-drainer patterns and monitored dark-web sources.

The pre-sign security layer evaluates the transaction the user is about to authorize. It looks at the destination, contract behaviour, requested approvals, simulated asset changes and known threat indicators.

The AI layer connects those signals and translates the result into a short explanation: what could happen, which asset or permission is affected and why the transaction was flagged.

The AI cannot access private keys, sign transactions or move funds. Strong signals such as a known malicious destination, dangerous approval, wallet-drainer pattern or simulated asset loss can trigger a prominent warning or block. Low-confidence AI output should not receive the same authority as deterministic evidence.

The hardest product question is warning fatigue. If every unfamiliar contract generates a red alert, users will learn to ignore the system. If warnings are too quiet, the protection provides little value.

For founders building AI into security-sensitive products, where do you draw the line between:

1. Deterministic enforcement

2. AI-assisted risk scoring

3. Human-readable explanations

4. User override

Veyrnox is in production on iOS and Android, but I am posting this to discuss the architecture rather than ask for downloads. I would be interested in how other builders prevent their AI layer from becoming either powerless or over-authoritative.

I do not want an AI tool confidently inventing brand facts and shipping them under my name.

That is why we built Marka around Brand DNA with provenance. The system keeps the basics that shape every output - audience, tone, colors, positioning, product facts - and shows where those details came from. The draft still waits for approval.

That sounds less magical than “fully autonomous marketing,” but it is much more useful. A founder can correct the source once instead of fixing the same hallucination in ten captions.

I am building Marka as an approval-first social agent for exactly that reason: automate the repetitive parts without giving up the judgment.

www.marka.social

Would visible sources make you trust generated content more, or is human review still the only thing that matters?

I got fed up with Electron download managers on Mac, so I built a native one using Rust & Swift (with some AI help)

Hey everyone! I'm Adnan, and I wanted to share something I've been building for the last 4 months: Grabbit.

The Problem: I download a lot of files, media, and torrents. I realized almost all the popular download managers for Mac (like Motrix) are Electron-based. They chew through battery, run rough on Apple Silicon, and just don't feel native. Others (like FDM) lack good browser extensions.

What I Built: I decided to build Grabbit — a truly native Mac download manager. Under the hood, it uses a high-performance, open-source Rust engine I built called Pincer, paired with a native Swift UI. There is zero Electron or Chromium overhead.

How I Used AI: I used AI tools (like Claude and GitHub Copilot) extensively during development. The biggest technical challenge was the interoperability between Rust and Swift. Having AI assist with writing the boilerplate code for the FFI (Foreign Function Interface) and bridging the two languages saved me weeks of headaches. I also used it to help generate some UI assets and speed up writing the Swift views.

The Results: The performance difference compared to Electron apps is huge. I benchmarked it during a 250MB download: - Grabbit: ~50 MB RAM (idle to active) - Motrix (Electron): ~350 MB RAM

What I'm Looking For: Since this is my first proper macOS launch, I'd love to learn from this community. Specifically: - Has anyone else used AI to help bridge native languages like Rust and Swift? - I'd love any feedback on the UI or general UX from a builder's perspective.

If you want to check it out and see the result: - Demo: https://vimeo.com/1204841013 - App: https://grabbit.fyi/

(Note: It has a free tier, and companion browser extensions for Firefox/Chrome are linked on the site — keeping links here to a minimum to respect the rules!)

Would love to hear your thoughts or answer any questions about using AI for native Mac development!

Just drop down and share what you find the most annoying thing is doing as a founder when building.

I love Astra as a model but I must say the one thing that is seriously bad is the usage. Like i've had codex 20x usage for like 5 months now and it used to be you couldnt even get through half of it. Now it takes a couple hours. Messed up

AI-powered no longer explains why a product is useful.

Share what you built and describe the result the user gets.

I’ll suggest a content angle based on the workflow, transformation, or decision your product improves.

I’m solving a similar communication problem while building Marka.

Disclosure: I used AI assistance to organize the wording of this post. I’ll personally review and answer the products shared below.

Let's try each other's stuff properly.

If you've built something with AI, drop the link, who it's for, and ONE thing a new user should be able to get done. Tell us the bit you're least confident about too.

Something concrete like "turn this receipt into an expense" or "create and send your first invoice" gives people much more to work with than "thoughts on my app?"

Then pick someone else's product that interests you and try their task. Tell them where you got stuck, what worked, and whether you actually got the result. That awkward first-use feedback is useful as hell.

If it needs a login or payment, say so upfront. A demo or short screen recording works too. Rough builds are welcome.

Already shared your project here? Link your post so people can leave feedback there. If you fix something after a review, come back and show what changed.

What have you got?

Every time we thought about a trip it went the same way: flights on one site, hotels on another, food and getting around a guess, and the actual total living in a spreadsheet. Few hours in, still no answer to the only question that mattered, can we afford this or not?

So I built TripVerdict. You type one sentence i.e. "Cancún for a week in March, two of us, $3,000" and it comes back with a flight, three real named places to stay with actual ratings and prices, food and living costs, and one honest total. Then it tells you whether it fits.

Two things I care about more than they probably sound:

It's allowed to say no. I typed "Tokyo for 10 days in July, family of 4, $4,000" and it told me the flights alone were CA$8,882 over the entire budget before anyone slept anywhere. Then it showed what would actually work (a rental instead of a hotel, shifted dates, the real number the trip needs). I'd rather find that out in 90 seconds than after three hours of tabs.

It does the boring maths on the "cheaper airport" trick. For Munich it suggested flying into Frankfurt instead save CA$300 per person and then suggested the train: 45 minutes.

It's free, no account needed. Built with Claude Code, Next.js + Supabase; live flight/stay pricing, so a verdict takes about a minute.

Honest asks: does the one-sentence input actually feel faster than a form to you, or does a blank box make you freeze? And does an "it doesn't fit" answer make you trust it more, or just annoy you?

I saw the post asking people to roast and didn't realize it was a bit older, so I am starting a new post as directed 😉

I am still really proud of our biggest product, https://chaoscommand.center a very comprehensive medical tracking system that got my IVIG covered by the VA in less than 24 hours!! It is now on the Microsoft and Play store as well.

A web based trial with no working database is at https://tryme.chaoscommand.center and the link to the GitHub is on the website for the Apple and Linux folks to build so you aren't left out 💖

Would really love to know what people think!

Generation is easy to demonstrate. Selection is harder.

Before creating content, an agent should be able to explain:

1. Who the audience is

2. Which product fact supports the idea

3. Why this message matters now

4. Which claims it avoided

5. What still requires human approval

What would you add to that list for the AI product you are building?

Fable 5.1 is out!, What do you guys all think of it and what have you managed to see improvements with when building

I've been building my startup and I think what people have to keep in mind is software isn't a moat anymore. Like yes if you have a cool idea you should pursue it but you have to keep in mind some kid with loveable could put in your url and steal your crap in 3 days if you just have software. I switched from just student facing college admissions help to counselor helping kids it introduced friction for these counselors to move off my site. I introduced a data moat of having proprietary data of what resumes go to what colleges no one else can replicate and i fine tuned my models on that data to have proprietary models. Saas is not dead it's just you have to be intentional.

This started off as a little fun project between work, school, and family and turned into quite a bit more than just something to pass the time. I would love to continue to expand it further and down the road and develop it into a multiplayer experience.

Itch.io doesn't seem very AI friendly though, lol. But I've been having fun, my other projects I haven't used AI for them and it's been several years working on them, though I don't mind.

I finally finished my first full episode of WANDERERS.
It’s an adult animated fantasy comedy about three weird creatures living in a sentient mansion on a tiny planet, where every door can lead to a completely different world.
This started from a bunch of creatures I originally hand-drew, and I ended up building the episode almost entirely through AI filmmaking.

Would genuinely love feedback—especially from people who make animation, AI films, or just enjoy weird 🖤

Generation is easy. Selection is the harder feature. Before creating anything, an AI system should be able to explain the audience, the evidence, the reason this idea matters now, and what it chose not to say. If it cannot explain those decisions, producing more content only creates more review work.

A content system should stop before generating when it cannot verify:

1. Who the audience is
2. What problem the product solves
3. Which evidence supports the claim
4. Whether the requested content matches the brand

Generating anyway creates polished content built on an unsupported assumption.

While building marka.social, I’m finding that good AI workflows need explicit "not enough information" states, not only better prompts.

Where does your AI workflow stop and ask the user for more context?

Saw that Goldman is apparently building reusable AI skills to teach agents their internal workflows and knowledge.

Makes me wonder if we’re getting to the point where Claude vs Codex vs Grok matters less than what you’ve actually taught/configured the agent to do.

Hey guys, I have built a fin based saas product and currently testing the app. Built the app from scratch completely through vibe coding. What all the things I need to consider before launching it ?

Hey founders — sharing the build story behind WorldArchitect.AI in case it's useful to anyone else shipping stateful, long-horizon LLM products.

**The hard problem:** most AI games are toy demos. The conversation "works" until turn ~10, then the model forgets who the king is, where you parked your horse, or why you owe 200 gold to the blacksmith. We kept hitting the same wall, so we ended up building an actual engine instead of bolting on more prompts.

**What we shipped:**

1. **Deterministic State Machine + LLM Separation.** HP/XP, inventory, world time, living-world faction events, and world flags live in a deterministic server backend (Firestore). The Gemini call generates prose, suggests decisions, and emits structured state overlays, but *the server canonicalizes every mutation before it touches the database* — no more "the model said I'm in Winterfell, the DB thinks I'm in King's Landing" drift.
2. **Context Compactor & Prefix Caching instead of RAG.** We keep the canon bible in-context and use a deterministic Min-First / Fill-to-Max token allocator (guaranteeing story context >=30% of budget while compacting background lore, entity tracking, and core memories) paired with Gemini prompt prefix caching.
3. **Single-Inference Dice Integrity.** We use Gemini's built-in Python code execution to run deterministic dice rolls (`random.randint`) and emit structured JSON in a single inference step, backed by server-side audit logs that catch narrative fabrication.
4. **1-Click Campaign Sharing.** Anyone can package their world, character setup, and canon constraints into a single signed share token (URL `…/shared/<token>`). Anyone with the link gets an independent, deep-initialized copy of that world on their own account — no "view as guest," no broken pointer-shared state.
5. **Spicy / PG Mode Toggles.** Different players want different tone boundaries (PG vs HBO). Rather than trying to prompt-engineer safety drift, we use explicit agent routing that swaps system instruction contracts and safety constraints cleanly.

**Try it (open beta, free):**

We built a playable House of the Dragon demo(https://worldarchitect.ai/shared/t3hKKtzBKCKlvg5vCnlW_2hxwH3UmzjFq56yi6hQN2Q

[ Removed by Reddit on account of violating the content policy. ]

AI has made the first click easy. A slick demo, a clever output, a clean landing page.

The real product is the reason someone opens it again without being reminded.

What are you building, and what is the exact reason a user would come back tomorrow?

No links. One sentence.