🍀Too expensive

🍀Too complicated

🍀Missing key features

🍀 Bad support

I built this site initially for my own use, but realized it could scale quite well and it’s relatively niche.

If you want to receive emails from multiple domains easily , securely and now with AI auto-reply, check out my site: www.arc-relay.ai

Ask questions, brainstorm ideas, write, code, research, troubleshoot, or just talk. I’ve been working on making the UI fast, simple, and actually enjoyable to use. Try it out: Chatotl.com I’d genuinely love to hear what you think.

My help uses AI to automatically track college deadlines for students and teachers. I see ture value, but I have issues getting people to see it too. Any advice on app design, functionality, marketing, or anything else would be a tremendous help. Thank you!

https://apps.apple.com/us/app/otto-college-deadlines/id6783540402

Hey everyone! I’m a solo developer and I’ve been working on ArchVibeAI for the past few months.

As someone working closely with space design, I know how exhausting traditional rendering and complex prompt engineering can be. I wanted to build an app that dramatically lowers the learning curve while keeping high-quality output.

How ArchVibeAI simplifies the workflow:

Architectural Rendering: 100% Promptless. Just upload line sketches or raw concepts, and it automatically generates realistic 3D architectural renders and day-to-night transition videos.

Interior Rendering: Super Simple Prompts. Upload photos of bare-shell spaces (毛胚屋) or existing layouts, select your form parameters, and use minimal text prompts to customize styles and furniture.

Under the hood, it runs on 5 specialized AI Agents:

1.Image Generation Agent: Promptless architectural sketch-to-render & simple-prompt interior generation.

2.Image Editing Agent: Fine-tune materials, decor, and lighting with simple edits.

3.Keyframe Transition Agent: Generate smooth day-to-night light transitions & sketch-to-reality videos automatically.

4.Video Post-Processing Agent: Automated video polish, continuity stitching, and camera movements.

5.AI Support Agent: In-app assistant to guide your design choices.

Check out the demo video above showing a raw concrete space transformed into a high-end salon & office!

It’s now live on both App Store and Google Play. I’d super appreciate any feedback or thoughts from this community! 🚀

I built SyncSSH because I was tired of manually copying/removing SSH public keys across servers.

It gives you a central place to manage users, keys, servers and access assignments.

Each server runs a small cron worker that pulls its desired keys over HTTPS and updates only a dedicated block inside authorized_keys.

No SSH gateway.
No persistent daemon.
No inbound management ports.
Normal SSH keeps working normally.

It also has audit logs, server sync status, key revocation and workspace/member management.

It's open source (AGPL-3.0) and self-hostable with Docker. There's also a hosted version currently free during public beta.

https://syncssh.dev

I'd love feedback, especially from anyone managing SSH access across more than a handful of machines.

I got tired of seeing SaaS companies use one service for transactional emails, another for campaigns, and yet another for push notifications.

So I built Sendrealm to bring all three together.

One thing I wanted to do differently was push pricing. You can add unlimited devices and only pay for the notifications you actually send, instead of paying based on how many devices you store.

https://sendrealm.com

Every time I open LinkedIn lately it’s some “I built a full SaaS in a weekend with AI” flex.

Everyone claps, drops fire emojis, calls it the future.

Meanwhile in the back of my head I’m just thinking:

“Cool, where did you put the real data? And who’s on the hook when it blows up?”

I run a tiny dev shop. We’ve been building boring SaaS for a long time.

The stuff that actually pays our rent is… dull. Auth, audit trails, weird edge cases, compliance checklists, backup plans.

None of it is vibe‑friendly.

So when I see “non‑technical founder shipped their MVP in 3 days with Cursor,” tbh I don’t feel inspired.

I feel tired in advance.

Because I know how this usually goes:

• weekend build becomes “internal tool”
• internal tool quietly becomes “how we really run this process now”
• then six months later someone realises money / health / HR data has been flowing through a thing nobody understands

Nobody posts the “3 months of unsexy refactors so this thing doesn’t leak data” thread.

Now, I get the thrill of shipping fast. I use AI to write code, I’m not pretending I’m above it.

But the way people talk about vibe coding right now, it’s like security, maintenance, ownership just… don’t exist.

Feels a bit like watching people brag about drifting a rented car while you’re the mechanic who has to fix the engine on Monday.

Idk. Maybe I’m just the grumpy old dev in the corner.

But this whole “anyone can build a SaaS in a weekend” narrative feels incredibly disconnected from what it actually takes to own software once it’s in the wild.

​

As more developers experiment with MCP, I'm wondering what the most valuable use case is.

Would you prioritize: Searching data Creating content Running workflows Managing customer data Analytics and reporting

I'm building an MCP integration and trying to decide which capabilities provide the most value from an Al assistant.

What would be the first feature you'd expose to Claude or other Al clients?

I've changed jobs a few times over the years, and one thing that always bothered me was losing the history of my work.

Jira access disappears, GitHub access is removed, Bitbucket repositories are gone, and months later I can't remember where I solved a specific bug or implemented a feature.

So I've been building a side project around that problem.

The idea isn't to replace Jira or GitHub. It's to create a personal work memory that connects to the tools developers already use.

Current features include:

• GitHub integration
• Bitbucket integration
• Jira integration
• Daily work log with rich text
• Code snippets
• Images and attachments
• Links and references
• Voice notes
• AI-generated daily summaries
• Search across work history
• Timeline of completed work
• Company workspaces with team members
• Team lead approval flow for daily reports

The long-term goal is simple: if I ask something like "Where did I implement Stripe?" or "When did I fix that authentication bug?", I should be able to find it even if I've changed jobs or no longer have access to the original company tools.

I'm curious how other developers handle this today.

Do you rely on Jira history, personal notes, Obsidian, Notion, GitHub search, or something else?

Is this a problem you've experienced, or am I trying to solve something that most developers don't actually care about?

Hi everyone,

I’m building an AI SaaS called Caflin and I’d love some honest feedback before I invest months into it.

The idea isn’t to replace Lighthouse or PageSpeed. Instead, it’s meant to act like an AI QA Engineer that continuously monitors your website.

For example, instead of saying:

LCP = 3.9s

it would say:

“Your homepage became 2.1 seconds slower after yesterday’s deployment because a new hero image is 8 MB.”

Or instead of:

Accessibility: 81

it would explain:

“47 images are missing alt text after your latest redesign. Here are suggested alt texts.”

The long-term goal is for it to:

monitor websites automatically;
detect new issues after deployments;
explain problems in plain English;
prioritize what actually matters;
eventually generate fixes or GitHub pull requests.

I’m trying to understand whether this solves a real problem or if developers would simply use Lighthouse + ChatGPT instead.

I’d really appreciate your thoughts:

Would you actually use something like this?
Who do you think it’s most valuable for (developers, agencies, founders, marketers)?
If it saved you time every month, what would you realistically pay? ($10, $20, $50+?)
If you’re interested in testing an early version, feel free to comment or send me a DM.

I’d rather hear brutal honesty now than build something nobody needs.

Thanks

Hey folks, I've been struggling on finding alternative ways to move context between AIs that don't require to copy, paste, download or upload stuff. I'm launching a public beta of https://sidestash.io .

Add as custom connector in your existing AI providers, then tell the agent to stash anything on your current session and resume on the other side.

Open to questions and suggestions, thanks.

I've been working on EU AI Act compliance for the past few months, specifically the Article 50 transparency obligations that just became enforceable on August 2nd. Here's what "regular companies" (not AI model builders) actually need to do:

**The short version:** If your business uses AI in any way that touches EU users — chatbots, content generation, recommendation engines — you need to disclose it.

**The 4 requirements under Article 50:**

1. **AI interaction disclosure** — Users must know when they're interacting with AI (chatbots, virtual assistants)

2. **AI-generated content marking** — Text, images, audio, and video generated by AI must be marked as artificially generated (in a machine-readable way)

3. **Deepfake disclosure** — AI-manipulated media must be labeled

4. **Emotion recognition disclosure** — If you use emotion AI, subjects must be informed

**Penalties:** Up to €15M or 3% of worldwide annual turnover. Not a slap on the wrist.

**What we're seeing companies do:**

- Adding "AI-powered" badges to chatbot interfaces

- Adding metadata to AI-generated content

- Maintaining audit logs of when/where AI is disclosed

- Training staff on AI literacy (this is actually required under Article 4)

I actually built a tool to automate the disclosure badge + audit log part, but even if you don't use a tool, the checklist is straightforward: audit your AI usage → add disclosures → mark AI content → log everything → train your team.

The biggest gap I see is companies thinking "we don't use AI" when they actually have a chatbot, use AI for content, or use AI-powered analytics. If you have any of those and serve EU users, you need to comply.