u/SunEconomy3251

Image speaks for itself. Tried using composer 2.5 as much as I could this billing cycle in an attempt to max out my $60 plan. Didn't max it out unfortunately! Better luck next month 😄

https://preview.redd.it/mk2m6xn08gbh1.png?width=1114&format=png&auto=webp&s=74710510c17f720511129149918ebe1b73c3c977

$60 Pro+ plan gives you on Composer 2.5:
682.4 M / 40.6% * 100% = 1.680.780.000 tokens a month

$60 Pro+ plan gives you on Auto:
299.7 M / 26% * 100% = 1.152.690.000 tokens a month

$60 Pro+ plan gives you on Composer 2.5 Fast:
18 M / 4.4% * 100% = 409.100.000 tokens a month

I love Composer 2.5, I've said it before & will keep repeating it: best value for money.

Thank you Cursor! 💯

Hey guys,

I’m selling the domain casinostarters.com — a short, memorable, and highly brandable name.

Why this domain works:

• 🎯 Perfect fit for online casino, iGaming, or gambling-related projects
• 🚀 Great for beginner guides, affiliate sites, or onboarding platforms
• 🧠 Easy to understand, easy to remember
• 🌐 Premium .com extension

Ideal use cases:

• Casino or sportsbook affiliate website
• “Beginner’s guide to casinos” content hub
• iGaming SaaS, tools, or review platform
• Community or newsletter for new casino players

Details:

• Domain: casinostarters.com
• Extension: .com
• Minimum offer: $600
• Registrar: Godaddy

Open to reasonable offers.
Comment or DM if interested — happy to answer questions.

Thanks!

Hey guys,

I’m selling the domain wantprofit.com — a short, memorable, and highly brandable name.

Why it’s valuable:

• 💰 Strong commercial intent (“want” + “profit”)
• 📈 Perfect for finance, investing, affiliate marketing, SaaS, or entrepreneurship content
• 🧠 Easy to remember, easy to spell
• 🌍 .com extension (gold standard)

Use cases:

• Personal finance or investing blog
• Online course or coaching brand
• Marketing / growth newsletter
• Startup or SaaS focused on revenue, monetization, or business growth

Details:

• Domain: wantprofit.com
• Extension: .com
• Minimum offer: $5.000
• Registrar: Godaddy

Open to reasonable offers.
Comment or DM if interested — happy to answer questions.

Thanks!

I’ve known a friend for about 11 years through internet marketing. Over the years, he often asked me about my niches, side projects, ideas, and about my main business in general. I was very open with him because I thought there was trust.

But several times, after I told him about a project or idea, he would start working on an almost exact copy the same day or shortly after. This happened multiple times. He never really succeeded with those copies, so I didn’t make a huge issue out of it at the time, but the pattern was obvious.

The strange part is that he never shared his own projects with me. Recently, when I asked him what he was working on, he said he doesn’t share because apparently I “copy his projects.”

That shocked me, because from my perspective it has been the complete opposite. I asked him to name examples of projects I copied, and I also mentioned three specific examples where he had copied my projects after I shared them with him.

Instead of giving any examples, he accused me of turning it around & attempting to “gaslight” him.

That really bothered me. I was open with him for years, he copied from that openness, and now when I confront him, he flips it around and acts like I’m the one who copied him & double downs on it like he believes his own lie.

At this point, I don’t trust him anymore and I want to end the friendship permanently. This feels beyond being unappreciative. To me, it feels dishonest, disrespectful and manipulative.

Am I overreacting for wanting to cut him off completely over this?

Update:

After I directly asked him to name what I supposedly copied from him, he still didn’t give any concrete examples.

Instead, after I listed specific projects he had copied from me, he replied by mocking me with crying-laughing emojis and basically said I was talking nonsense. Then he flipped it around again and said something like: “So I copy from someone who copies,” implying that I was the original copier?!?!

When I challenged that, he didn’t provide proof or examples. He just said things like “Can you twist that?” and “That would be hypocritical,” again trying to make me defend myself instead of answering the actual question.

At that point I sent him a final message saying I no longer trust him, I don’t want contact anymore, and I’m done with the friendship. Then I blocked him.

Thanks to all of you for the advice

A lot of SaaS teams talk about vendor lock-in like it is some unavoidable law of nature. A friend of mine did as well after rebuilding his app 3 (!!) times in a row. However most of the time, it is not.

A lot of it is self-inflicted by teams that build fast on top of managed platforms without ever asking: “Could we actually move this thing if we had to?”

The issue is not using AWS, GCP, Azure, Vercel, Firebase, Supabase, Cloudflare, Stripe, OpenAI, etc. The issue is building your entire product in a way where the vendor becomes your architecture.

Common mistakes I see 90% of people make:

1. Treating serverless as the foundation instead of the elasticity layer

Serverless is great for burst capacity, async jobs, webhook fanout, scheduled tasks, image processing, event glue, and spiky workloads.

But if your entire domain model, routing, auth, queues, business workflows, and persistence are fused into one vendor’s serverless ecosystem, you are not just using serverless. You are renting your application framework from that vendor.

The core platform should be portable and reproducible. Serverless should be replaceable.

2. Hardcoding vendor assumptions into business logic

Your app should not be full of assumptions about one provider’s event format, queue behavior, IAM model, retry semantics, storage API, function timeout, auth token shape, or model response format.

Once those details leak everywhere, migration becomes a rewrite.

Wrap vendor-specific stuff behind boring interfaces. Make the product logic unaware of where it runs.

3. Not owning the database strategy

People say “we use Postgres” but actually depend on a vendor’s backups, replicas, auth, restore process, private networking, monitoring, extensions, connection poolers, and failover behavior.

Postgres is portable. Your operating model might not be.

If you have never restored your database somewhere else, you do not have a backup strategy. You have a hope strategy.

4. No real infrastructure-as-code

ClickOps is how lock-in quietly becomes permanent.

If your infra cannot be recreated from code, reviewed, versioned, and tested, you do not really own it.

Terraform, OpenTofu, Ansible, Nix, Kubernetes manifests, Nomad jobs, Docker Compose, whatever. Pick your poison. But the environment should be reproducible without someone remembering which buttons they clicked six months ago.

5. No local or neutral runtime

If the app cannot run outside the vendor’s environment, that is a warning sign.

You should be able to run core services locally or in a neutral staging environment. Maybe not every managed integration, but enough to prove the app is not spiritually dependent on one platform.

If “works on Vercel/Firebase/Lambda only” is the architecture, good luck.

6. Making proprietary services the source of truth

Using managed auth, analytics, queues, object storage, feature flags, or event systems is fine.

Making them the only source of truth with no export path, no mirror, no replay, no abstraction, and no fallback is where things go bad.

Your critical state should be portable. Your events should be replayable. Your files should be syncable. Your users should be exportable.

7. No migration drills

A lot of teams discover they are locked in only when they need to leave.

By then, the person who set everything up is gone, the docs are stale, half the state lives in vendor dashboards, and nobody knows what breaks if they touch DNS.

Do small migration drills before you need them:

• restore prod backup into another environment
• mirror the DB
• replay events
• sync object storage
• rebuild infra from scratch
• run workers somewhere else
• test DNS cutover
• verify rollback

You do not need to migrate every month. But you should know that you can.

8. Confusing “managed” with “magic”

Managed services are useful. They save time. They reduce operational burden.

But they do not remove the need to understand what is happening underneath.

If nobody on the team understands networking, replication, queues, backups, failover, DNS, observability, or deployment mechanics, the vendor is not just a tool. The vendor is replacing your missing competence.

Aka skill lock-in.

9. Building AI features directly around one provider

This is the new one.

Teams are hardcoding one model’s tool-calling format, prompt structure, embedding dimensions, moderation behavior, JSON quirks, pricing assumptions, latency profile, and eval tooling directly into the product.

Then they act surprised when switching model providers is painful.

LLM providers should be adapters. Your product should own prompts, evals, routing, fallbacks, logging, redaction, and data boundaries.

10. Optimizing only for launch speed

This is the root of most of it.

The team ships fast by gluing together high-level services. That is not automatically bad. Early-stage products need speed.

But every shortcut should come with a question: “How do we leave this if pricing, reliability, compliance, or strategy changes?”

If the answer is “we will figure it out later,” you are choosing lock-in. Maybe that is fine. Just be honest about it.

My take:

Vendor lock-in is usually not caused by using vendors.

It is caused by not maintaining an exit path.

Use managed platforms. Use serverless. Use cloud services. Use AI APIs. Use whatever helps you ship. But at least own your foundation...

Keep your core portable. Keep your data exportable. Keep your infra reproducible. Keep your workers idempotent. Keep your business logic separated from vendor glue.

Hey all,

I made a browser-based site for file conversion, compression, and everyday utility tools.

The goal is to make common file tasks easier without installing random desktop software. Things like converting PDFs, images, video/audio files, spreadsheets, JSON/CSV/XML, compressing files, OCR, background removal, QR tools, JSON formatting, and similar small utilities.

I’d really appreciate people testing it with non-sensitive files and reporting bugs.

I’m especially looking for:

• Conversions that fail
• Bad or weird output files
• Confusing UX
• Missing formats
• Anything that makes the site feel untrustworthy

Site: fileconversion.co

I’m the creator, so blunt feedback is welcome.

Thank you!