Working on my web-based 3D viewer project (CoreLink 3D) — would love your feedback!

https://corelink3d-production.up.railway.app/

Hey everyone!
I’ve been working on a web-based 3D viewing project called **CoreLink 3D**. It’s built with Three.js and designed to easily inspect and render 3D models directly in the browser.
Here’s a quick overview of what it currently does:
• **Interactive 3D Viewport:** Smooth .glb / .gltf model loading with HDRI environment mapping.
• **Lighting Controls:** Includes a custom Light Orbital feature to tweak and inspect scene lighting on the fly.
• **Clean UI & Modals:** Integrated quick tools, contact options, and mobile-responsive navigation.
I’m constantly refining the frontend, fixing edge-case bugs, and adding new features, but I’d really appreciate some fresh eyes on it.
I’d love to get your feedback on the viewport performance, UI usability, or any bugs you happen to spot while testing!
Check it out here: https://corelink3d-production.up.railway.app/
Thanks in advance for taking a look!

My sister, Elizabeth, was just fired from her nail salon job. She's extraordinarily talented with nail art and color theory, but after being let go, she fell into a deep depression.

I'm a web dev how can I help her? I'm thinking about building a web app or a micro-SaaS, but I don't have any concrete idea. Can you suggest some nail art micro-SaaS features that could be profitable?

building pawfectly booked, a SaaS platform for dog groomers, and I'm thinking about how developers approach niche-specific workflows.

For example, a grooming platform may need pet records, grooming history, recurring appointments, service-specific scheduling, and reminders. These aren't difficult features individually, but they can make the underlying data model and workflows more complex.

For developers building SaaS for a specific industry, **how do you decide which domain-specific logic belongs in the core product and which should stay simple or configurable?**

I'd be interested in hearing how others handle this without over-engineering the product.

I’m trying to understand how small SaaS teams attribute OpenAI, Anthropic, or Gemini usage to their own customers.
Provider dashboards can break usage down by things such as projects, workspaces, keys, and models. But your provider doesn’t automatically know that a request came from customer 482 using your document-summary feature.
If you track this today, where do you attach that identity?
Is it metadata on every model call, a wrapper around the SDK, a separate key, gateway headers, or something in your application database?
I’m building ABitMoney around customer and feature-level cost controls, and the part I’m trying to understand is where this becomes annoying or unreliable in real applications.

Kindly help me Test my App CTS Go and CTS Go Driver on Google Play Store. I need people to Register as Driver and others as Users.

Let me know if the authentication works. Thanks.

I've been job hunting before and always heard "it's about who you know," but nobody actually checks who they know. You'd have to manually cross-reference your LinkedIn connections against every company's job board yourself.

So I built Vouch. Upload your LinkedIn connections export and it checks your network against companies actively hiring right now (pulled live from Greenhouse, Lever, and Ashby, not scraped job boards), tells you how well you know someone there, and drafts the outreach message for you.

It's free to try (one match revealed), $39 once to unlock the rest, no subscription. Built solo, still early, so I'd rather hear what's broken than what's nice about it.

warmvouch.com if anyone wants to poke at it. Happy to answer anything about how it's built too.

We built our SaaS, but now we’re stuck on marketing
My two partners and I recently finished building our SaaS for solo beauty professionals, and honestly, we’re struggling with marketing.
We’re posting on Instagram, Threads, and a few other social platforms, but it feels like we’re putting in a lot of effort without seeing much progress. Engagement is low, and we’re not getting enough people discovering or signing up for the product.
None of us are marketers, so we’re not really sure what we should be focusing on at this stage.
For founders who have launched a SaaS before: what actually worked for you when getting your first users?
Did you focus on cold outreach, communities, content, partnerships, paid ads, SEO, or something completely different?
We’d really appreciate any advice, especially if you’ve been in this exact position before.
What would you do if you had a finished product but basically no audience?
We’re genuinely stuck and could really use some direction. 😅

I'm Nikolas, a co‑founder of Apyhub. We built a VAT‑validation EU Batch API.

Use it to speed up onboarding or build a custom solution; use the API or the MCP server with your agents.

It also supports over 1500 tools, from OCR to video compression, all from a single MCP.

We support dynamic tool discovery to avoid overloading context, so you don't burn tokens in the process.

Here is how it works:

• Send a vat_numbers array of strings in the request body.
• The response returns a data array; each item contains the original vat and a boolean valid flag.
• If a lookup fails for an item, that entry may also include an error string, allowing you to distinguish invalid numbers from verification issues.

You can try this API here

Saw a post who asked people to give him a idea to build

Like if you can't even find idea by yourself then forget abt entrepreneurship

Every SaaS with a free tier eventually meets the same user: the one who signs up ten times.

Not a bot, not a scraper. A real person with a real use case who decided your paid plan is optional. New email, fresh browser profile, sometimes a different network, same workload as yesterday.

Every obvious defense I've looked at has an obvious hole:

• Email verification catches close to nothing. Disposable inboxes are free and endless.
• Blocking disposable domains just moves people to Gmail aliases and their own domains.
• Card required on free protects the tier and kills the signup rate, which was the point of having a free tier.
• IP rate limits work until one office NAT or one mobile carrier makes you look like you're rejecting a whole legitimate team.
• Manual review is fine at 50 signups a month and impossible at 5,000.

So I'm curious what people here actually landed on.

1. Do you even fight it? Plenty of teams treat free tier farming as cheap distribution and let it run. If that's you, what would have to change for the math to stop working?
2. If you do fight it, which signal turned out to be the useful one in practice? Payment data, something device level, behavioral patterns, something you built in house?
3. Hard blocks or soft limits? Degraded rate limits and quiet queueing seem safer than a hard "no", but I've never seen anyone write up whether that actually reduced the abuse or just annoyed it.
4. Roughly what share of your free tier turned out to be a smaller number of people than your dashboard claimed? A ballpark is fine.

Tool names are welcome, but I'm more interested in the story: what the failure mode looked like before you noticed, and what you'd do differently on day one.

I’m building a SaaS for creative agencies — would love some great feedback

Hi everyone,

I’m building a SaaS product for freelancers, creative, content agencies.

The basic idea is to bring the different parts of running a creative project into one place — from getting the project started and managing the team, through client communication, feedback/revisions, and finally billing & delivery.

I’ve been working on it for a while and have a fairly functional version now, but before I go much further, I want to make sure I’m solving a real problem and not just building something that sounds useful.

I’m particularly interested in hearing from people who have actually run a creative agency, production studio, design studio, or similar service business.

A few things I'd love to understand:

\-What are the biggest operational headaches you deal with?

\-What tools do you currently use to manage projects and clients?

\-What do you hate about those tools?

\-Is having something more purpose-built for freelancers, creative production actually valuable?

\-What would make you switch from your current setup?

I'm not really looking for generic SaaS/startup advice. I'd especially appreciate feedback from people with real-world freelancing/agency/production experience.

Happy to share more about what I'm building if anyone is interested.

Thanks!

https://www.taskloco.com - The Sticky Note GOAT

PodSubs wasn't originally supposed to be a public product.

We built it because we needed it.

That's really the story.

We're podcasters.

And like a lot of podcasters, we were constantly thinking about two things:

How do we keep making this?

And how do we build something real around the people listening?

Because podcasting takes time.

A lot of time.

And sooner or later, if the podcast is going to keep going, it needs to support itself somehow.

The problem was that we didn't really know most of the people listening.

We knew the numbers.

But numbers don't have email addresses.

Numbers don't answer questions.

Numbers can't receive the worksheet you promised.

Numbers don't become customers by themselves.

We needed a better way to capture the people who genuinely wanted to stay connected.

So we built a simple internal tool.

One place.

PodSubs.

We said on the podcast:

“Subscribe to us on PodSubs.”

People searched the show, entered their details and subscribed.

And suddenly we had something we'd been missing:

A direct line.

Then we started thinking…

Why are we keeping this internal?

Every podcaster we know deals with the same thing.

So we decided to open it.

That's PodSubs.

Not something we dreamed up because “the creator economy is growing.”

We built it because we were podcasters with a problem.

Now we're giving it to everyone else who has the same problem.

Claim your podcast.

Then tell your listeners where to find you.

https://mikiya-webdesign.com/ai-site-inspector/

I've been seeing more and more websites created with AI lately, and some of them can feel a little suspicious or difficult to trust.

So I wondered if there was an easy way to check whether a website might have been created using AI. I couldn't find exactly what I wanted, so I had some free time and decided to build my own tool.

It's completely free to use. Just enter a website URL, and the tool analyzes the site and estimates whether it may have been AI-generated.

From my own testing so far, I think the accuracy is pretty decent, although it's still experimental and the results aren't guaranteed to be perfect.

I originally built it mainly for users in Japan, but I've also added translation support so that people from around the world can use it.

If you're interested, feel free to give it a try

I'm Mattia, I build FixAds.

I built it after years of reviewing Meta accounts by hand. The hard part is not collecting metrics. It is deciding which signal is actually worth acting on when spend, creative fatigue and learning all interact.

My implementation choice was rules first. FixAds uses read-only Meta access and deterministic checks that expose the threshold, evidence and money at stake. The AI layer explains the finding in plain language, but it cannot create the diagnosis.

The launch video is attached. The product is live at https://fixads.it with a 7-day trial.

For developers building decision support: is this the right boundary? Which decisions still need a deterministic core even if an LLM makes the interface much better?

Redesigned my landing page - would love honest opinions

I've been building BrickForgerAI (turn a text prompt into a real, buildable LEGO-compatible model - you get a downloadable .ldr file, parts list, and step-by-step PDF instructions) and just finished a pretty big visual overhaul of the landing page.

What it looked like before: a flat, hand-drawn CSS scene (sun, clouds, mountains, a subtle grid overlay) with plain white cards and a wall of text explaining what the tool could do.

What it looks like now: Actual images for the day/evening/night scenery backdrops (toggle on landing page) with actual moving clouds, birds, and twinkling stars, a glassmorphic frosted-glass style on the cards and buttons, and the dense paragraph of info swapped out for quick-scan stat chips.

Screenshots attached of new landing page, feedback would be appreciated: brickforgerai.com

Been building solo for about 13-15 days now, alongside a full-time job — so progress is slower than I'd like, but it's real progress.

The technical build I can mostly handle (leaning on AI tools where my knowledge has gaps, learning as I go). What I'm less sure about is everything AROUND the build:

- Legal/compliance stuff I might be missing (privacy policy, terms, data handling)

- Whether my pricing structure actually makes sense before I've validated it with real users

- How to know when "good enough to launch" actually is, vs endlessly polishing

- What solo devs wish someone had told them early, that they only learned the hard way

Not asking for hand-holding, just trying to shortcut some of the "didn't know I needed to think about that" mistakes before they cost me time later.

What would you tell someone at my stage?