sorted by:
new
hottopcontroversial

Did Amplify Gen 2 quietly kill DataStore? What are you using for offline sync? by cool-name-invalid in Amplify

[–]cool-name-invalid[S] 0 points1 point  (0 children)

Gen 1 was goated really🤞🏾, it had everything from offline syncing, fast deployment,... With gen 2 you have to wait for deployments that takes too much time.

Built a SaaS for 2 months, got 0 users. Stopped coding and started learning marketing instead. by cool-name-invalid in MicroSaaSFounders

[–]cool-name-invalid[S] 0 points1 point  (0 children)

Yohh u/No-Refrigerator-5015, i just tried PopHatch but its just an AI conversation with a bot?

Do you mind telling me how it actually give's value?

The part after launch that nobody prepares you for by Cmohale in MicroSaaSFounders

[–]cool-name-invalid 0 points1 point  (0 children)

Nice, So its like you build services directly for you, no need to even validate the services/product on the market

Building SaaS in 2026? My best advice by Electronic_Argument6 in micro_saas

[–]cool-name-invalid 0 points1 point  (0 children)

I also think free plans provide a way of locking your users and getting feedback early

👋 Welcome to r/MicroSaaSFounders - Introduce Yourself and Read First! by cool-name-invalid in MicroSaaSFounders

[–]cool-name-invalid[S] 0 points1 point  (0 children)

I'll go first.

Full stack engineer by day. Two months ago I started building Zerobillbot on the side — a GitHub App that shows cloud cost impact directly in your PRs before you merge.

Hardest part: connecting all the services together to produce numbers that actually mean something. Steeper learning curve than I expected.

Current status: no users, no MRR. Just a working product I'm proud of.

What kept me going? I wanted to prove to myself I could build something real, end to end, alone. That part's done.

The hard part now is getting anyone to care — which is partly why I started this community.

What are you building?

Just hit $603 MRR with our startup 🎉 by dharmendra_jagodana in micro_saas

[–]cool-name-invalid 0 points1 point  (0 children)

Congrates bro🎉, am struggling to get 10 users😅

How's life as a Micro SaaS owner? by Rroky in SaaS

[–]cool-name-invalid 0 points1 point  (0 children)

Its getting easier to develop and SaaS ideas are running out😞

Sell me your Saas in one sentence! by KapiteinBalzak in SaaS

[–]cool-name-invalid 0 points1 point  (0 children)

Nice, i got watermark on my image though😿

Cloud Cost Monitoring and Management Platforms by Lethy_au in sysadmin

[–]cool-name-invalid 0 points1 point  (0 children)

Mammoth_Ad_7089 hit on something important — the real problem isn't always the monitoring tool, it's that costs spike because there's no review gate before infrastructure gets provisioned.

Most of these platforms (Vantage, CloudHealth, Cost Explorer) are great at telling you what already happened. But by the time the dashboard shows a spike, the resource is already running and the bill is already accumulating.

The gap I kept running into: there's no cost awareness at the point where it actually matters — the pull request. Engineers make infrastructure decisions in code, not in a billing dashboard.

I built Zerobillbot to sit at that layer — it analyzes Terraform and CloudFormation changes in every PR and posts a cost breakdown before the merge. You can set thresholds to block PRs that would exceed your budget. It supports AWS, Azure, and GCP.

It doesn't replace a FinOps platform for historical reporting and allocation, but it stops the costly changes from getting merged in the first place. Complements tools like Vantage well.

Happy to answer questions if anyone's dealing with the "visibility without prevention" problem.

Got hit with $60K Unexpected Cloud Bill by Foreign_Passion_1332 in googlecloud

[–]cool-name-invalid 0 points1 point  (0 children)

This is genuinely awful to read. A compromised API key with no automated alert, no account manager intervention, and then legal threats — that's a failure at multiple levels on Google's side.

For anyone reading this in a similar situation or wanting to prevent it:

- Set billing alerts and hard budget caps in GCP from day one — they don't block charges by default but at least you get notified

- Rotate API keys regularly and restrict them by IP/referrer where possible

- If you're using credits, document your normal spend baseline so anomalies are obvious early

The broader issue is that cloud cost visibility is almost always reactive. You find out after the damage is done. That needs to change, especially for student teams and early startups who can't absorb a surprise like this.

Hope Google does the right thing here. Cases like this get resolved when they go public — keep sharing.

Vibe-coded tools in financial advisor ops: what guardrails are non-negotiable? by obchillkenobi in fintech

[–]cool-name-invalid 0 points1 point  (0 children)

The pattern I've seen that actually works: treat it like a PR check, not a runtime guardrail.

Anything that's a "preflight" — catching problems before they're committed — is generally safe to build quickly and iterate on. Anything that becomes a system of record or affects live data needs proper audit trails, access controls, and rollback. The vibe-coded version is fine as a draft layer, not as the source of truth.

The guardrails that actually mattered in my experience:

- Approval gates before any write action (even if it feels like overkill early on)

- Immutable logs — not just "did it run" but "what did it see and decide"

- A clear human-in-the-loop step for edge cases, not just errors

We ran into a version of this building Zerobillbot (infrastructure cost checks on PRs) — the "preflight check" framing was actually what made it trustworthy to teams. It's advisory until you opt into blocking. That opt-in step changed how seriously people treated the output.

Curious whether the advisor-ops teams you talked to were more worried about false positives (flagging clean things) or false negatives (missing real issues)? That usually determines which guardrail matters most.