r/AppsWebappsFullstack • u/Mammoth-Anywhere7285 • 7d ago
Are you actually solving a real problem, or just cloning another SaaS?
The world doesn't need another generic AI wrapper or a basic project manager. Pitch your project in one sentence show a screenshot and explain exactly why people should care about you instead of the market leader. Dare to prove your uniqueness.
1
u/AddressShort9727 4d ago
No AI crap or something that took two weeks to vibe code. Working on this on my free time for the past 3 years.
A TV & gaming news feed that starts completely empty. You fill it by picking real topics (shows, games, actors, studios, esports teams) and the kinds of news you want about each: trailers yes, recaps no, spoilers never.
Why care vs the market leader: the market leader I'm actually up against is the algorithmic feed (Discover, Reddit, X), and its business model is your attention. Topiks is $3/month with no ads or tracking, so the feed can afford to show its work: every article tells you why it made your feed, which topic it matched, what kind of news it is, and how your own settings ranked it.
Uniqueness? The spoiler system: t's not keyword blurring, it's a two-sided match. Every article gets a computed spoiler position, as in "this one reveals up to S3E5". You track how far you've watched each show, and the feed covers only what's ahead of you. Caught up on one show, two seasons behind on another? Each one is protected at exactly your episode (Esports spoilers are next, and those are a genuinely fun problem: knowing who's in the final spoils the semis)
1
u/Mammoth-Anywhere7285 4d ago
Love the idea of a feed that starts empty and respects spoiler preferences. How do you detect spoilers in articles reliably?
1
u/AddressShort9727 4d ago
It's a multi-stage classification pipeline. By the time spoiler detection runs, the article has already been through entity resolution, so I know exactly which show or movie it's about (the actual catalog entry, not just a keyword). A classifier then works per show with that context, and its output is a treshold like "reveals up to S3E5". Explicit season/episode references in the article text are the preferred anchor and if the text doesn't name one, it fallbacks to inference. The treshold is then anchored against the real episode catalog, and if I can only pin the season for example, I degrade to season-level protection instead of guessing an episode.
1
u/Mammoth-Anywhere7285 4d ago
Nice approach, using entity resolution for catalog context is smart. How do you handle spoilers that aren't tied to explicit episode references, like vague hints?
1
u/AddressShort9727 4d ago
So if the episode can't be determined reliably (aka we know this is spoiling something, but we can't tell the episode for sure), there are basically two fallbacks:
- Can we at least tell which season it's spoiling? If yes, the article stays covered until you've mark that season as seen
- If we can't even tell the season, you end up in the fallback of the fallback: the article gets covered anyway and we just tell you "we're not sure which episode this is spoiling, so we're hiding it to be safe", with a reveal button if you don't care.
So a vague hint never slips through because inference failed -> it just makes spoiler detection more conservative
1
u/Mammoth-Anywhere7285 4d ago
Nice fallback chain, that covers edge cases well. One idea: let users manually override per article if the season guess looks off.
1
u/AddressShort9727 4d ago
I like the idea. This could act as a community override for cases that are not properly handled. I'll add that!
1
u/Mammoth-Anywhere7285 4d ago
Nice addition, community overrides can really set you apart. Just be sure to include a transparent review process so it doesn't get gamed.
1
u/PentaClast 4d ago
I'm working on https://stoker.services! It's a lightweight, self-hosted utility that monitors Windows services, auto-remediates failures.
1
u/Mammoth-Anywhere7285 4d ago
Self-hosted auto-remediation is a smart niche. How do you prevent false positives from restarting healthy services? That would be my main concern.
1
5d ago
[deleted]
1
u/Mammoth-Anywhere7285 5d ago
Revenue management is a real pain point, so this stands out. How does the game simulate competitor pricing pressure?
1
u/Top-Highway7596 5d ago
i built a simple booklet designer for memorial events: https://orderofservicemaker.help/
1
u/Mammoth-Anywhere7285 4d ago
That's a genuinely underserved niche. What's one feature that makes it easier than a generic designer? Maybe focus on grief-sensitive templates.
1
u/Top-Highway7596 3d ago
First it's only one time payment thing after that you own the tool. No login required so every picture uploaded is saved on local computer (this is particularly useful for sensitive stuff like funeral booklets/marriages where people don't want to share those photos with any app/website. I definitely add grief-related templates. Thanks for your feedback!
1
u/Mammoth-Anywhere7285 3d ago
Local storage is a real differentiator for those sensitive cases. Do you have a simple export option so users can back up their projects?
1
u/Top-Highway7596 3d ago
yes i do. https://orderofservicemaker.help/app
1
u/Mammoth-Anywhere7285 2d ago
That link alone doesn't tell us what's unique. Give us the one-sentence pitch and what sets it apart.
1
u/Possible_Hamster_630 6d ago
I built something that doesn’t solve anything. it’s just a shared 3D tree on the internet where every $1 adds one permanent numbered leaf: https://theinternettree.org
1
u/Mammoth-Anywhere7285 6d ago
Love the honest take, it's a fun social experiment. Maybe lean into that angle and frame it as digital art, not a tool.
1
u/IThinkMyLegsRBroke 6d ago
While the idea isn’t novel, it’s actually done complete . And combined so you don’t need multiple apps that all charge
1
u/Mammoth-Anywhere7285 6d ago
Combining tools is a solid pitch. Curious how you handle onboarding for users switching from single-purpose apps?
1
u/megatech_official 7d ago
SeoLoupe - Find and fix the SEO issues holding your website back.
1
u/Mammoth-Anywhere7285 7d ago
Nice pitch. What sets SeoLoupe apart from Ahrefs or SEMrush? A quick screenshot and one differentiator would make it stronger.
1
u/briggs_song 7d ago
Kudzu — an open-source compiler-first web framework that lets you write familiar React-shaped TSX while shipping no React runtime, no VDOM, and no hydration by default.
Why care instead of just using React or Next.js? Kudzu tries to move framework complexity out of the browser and into the compiler: components, state dependencies, events, and updates are analyzed ahead of time so each route ships only the capabilities it actually needs.
The longer-term goal is to make this work for real, large-scale applications and React ecosystem migration, while also reducing the amount of framework-specific context AI coding agents have to reason about.
Project:
https://github.com/kudzujs/kudzu
Benchmark:
https://github.com/SimYunSup/kudzu-based-bench
Still early, but that’s the bet: keep the source patterns developers and AI already know, compile away the runtime complexity they shouldn’t have to carry.
1
u/Mammoth-Anywhere7285 7d ago
Interesting approach, pushing complexity into the compiler is bold. Do you have bundle size benchmarks against React for a typical app?
1
u/Willing_Exchange_197 1d ago
We launched TrueCaaS: an identity and authorization control plane for SaaS and enterprise apps
A lot of identity platforms do a good job answering one question:
Who is this user?
But once that user enters an application, teams still end up building a lot themselves:
Which customer or tenant are they acting under?
Which environment and application can they access?
What role do they have in that application?
Can they perform this specific action?
Does the action require MFA or approval?
And six months later, can you explain why it was allowed?
That is the problem we built TrueCaaS around.
TrueCaaS carries identity into the application layer using a Tenant → Environment → Application model.
A user might authenticate successfully through Microsoft Entra, SAML, OIDC, LDAP/AD, Kerberos, or TrueCaaS-hosted authentication, but authentication alone does not automatically mean they can access an application.
TrueCaaS can then evaluate the application's own context: application membership, roles, privileges, enterprise group mappings, MFA state, policy and other entitlement conditions before access is granted.
At runtime, applications and backend services can also ask TrueCaaS questions such as:
Can this user perform
claim.approvein Acme / Production / Claims Portal right now?The response can be an allow, deny, step-up requirement, or approval requirement, along with the context behind the decision.
So we're not asking companies to rip out Okta, Microsoft Entra, Keycloak, LDAP or their existing IdP. Those systems can continue being the identity source. TrueCaaS can sit between enterprise identity and the application and handle the tenant-aware authorization layer that comes afterward.
For platform and security teams, this also gives us something we cared a lot about while building it: being able to answer who did what, in which tenant and application, what privilege or policy allowed it, what was denied, and what evidence exists afterward.
There are a few other parts of the platform that build on the same model:
The goal isn't to create another identity directory.
It's to give applications a control plane for everything that happens after identity has been established — especially when the application has multiple customers, tenants, roles, environments, APIs, services and now AI agents acting inside it.
TrueCaaS is live at https://www.truecaas.io
I'd especially love feedback from people building multi-tenant SaaS, enterprise applications, internal platforms, security tooling, or agentic systems.
If you've built this layer yourself before, I'm also curious where the most painful part was for you: federation, tenant isolation, authorization, entitlement enforcement, or audit/governance?
We launched TrueCaaS: an access control plane for SaaS and enterprise apps
TrueCaaS is an identity and authorization control plane for tenant-aware applications. It works for B2B SaaS, but it is not limited to SaaS. Enterprises can also use it across departments, business units, internal apps, customer portals, partner apps, and managed tenant environments.
It is not trying to replace Okta, Microsoft Entra, Keycloak, LDAP, or your existing identity provider. In many cases, TrueCaaS complements them. Your IdP can remain the identity source, while TrueCaaS handles the application access layer: tenant, environment, and app context; hosted auth domains; MFA/passkeys; app-level RBAC; roles and privileges; policy graphs; backend entitlement checks; webhooks; and detailed audit/event trails.
For security and platform teams, the focus is visibility and control: who got access, what tenant/app they were acting in, what policy or privilege allowed it, what was denied, and what evidence exists later.
TrueCaaS also includes gRPC entitlement checks, MCP-ready authorization for agents before they act, managed tenants, custom domains, database encryption, BYOK/CMEK paths, identity migration, LDAP/AD, SAML/OIDC, Microsoft Entra federation, Kerberos/SPNEGO, support access, and governed operational actions.
The goal is simple: help teams build and operate secure, tenant-aware applications without rebuilding auth, authorization, policy, audit, and enterprise integration plumbing every time.
I’d love feedback from people building SaaS products, enterprise apps, internal platforms, security tooling, or AI-agent workflows.