u/barmatbiz

I’m selling a specific product, but customers keep asking about it so much that I can’t focus

After building many Shopify stores for myself and for clients, I've tested a lot of themes, page builders, and tools.

I've found that the most flexible approach isn't buying another premium theme it's using AI to build a fully custom Shopify theme.

Here's the workflow I'm using:

1. Create the store design. You can use Claude to generate complete page designs, including the homepage, product page, collection page, and more.
2. Set up your development environment by installing the Shopify CLI.
3. Open your project in Claude Code or Codex.
4. Provide the AI with your design and write a detailed prompt describing how you want the theme to work.
5. Let the AI generate and customize the Shopify theme, then iterate until everything matches your vision.

This approach gives you complete control over your store instead of trying to customize an existing theme.

I'm still experimenting with this workflow, so if I'm missing any important steps or if you have suggestions to improve it, I'd love to hear your thoughts.

I have a complex design generated using AI, but the quality is low, so I need to remove and adjust parts of it to align properly for a t-shirt

tell us about a Funny, strange, educational, whatever you want about small taxis 

I own three apartments, and the constant stream of questions is starting to get on my nerves. I don’t want to come across as rude, but I’m concerned about losing customers or getting bad reviews. I’m considering options like delegating tasks or automating responses.

I own three apartments, and the constant stream of questions is starting to get on my nerves. I don’t want to come across as rude, but I’m concerned about losing customers or getting bad reviews. I’m considering options like delegating tasks or automating responses.

I have three apartments, and I'm getting annoyed by the constant messages with questions. I don't want to be rude, but I’m worried I might lose the customer and get a bad review.

Looking for Vercel alternatives to deploy a full-stack app.

Posting this because I spent months searching for an honest breakdown and couldn't find one. Hopefully this saves someone a few invoices.

The context

We're a small SaaS — Next.js app, ~600 daily active users, a few API-heavy routes. Nowhere near enterprise scale, but past the "just testing an idea" phase.

Vercel was the obvious choice at the start. Zero config, git push to deploy, free tier was generous. No regrets about starting there.

Then the bill hit $1,800 in a single month. No traffic spike. No viral moment. Just... growth.

The thing nobody says about Vercel

Vercel doesn't sell hosting. They sell simplicity. That's a real product with real value — especially when you're moving fast and have no ops experience.

But here's what they don't put in the hero section: Vercel is an AWS wrapper. Your functions run on Lambda. Your assets live on S3 and CloudFront. Their edge network is AWS's global infra. You're paying a 5-10x markup for the dashboard, the DX, and the git integration.

Again — worth it early on. Not worth it once you actually understand what's running under the hood.

Why we didn't just "optimize"

First instinct was to squeeze more out of Vercel — better caching, reduce function invocations, etc. We did some of that. Knocked the bill down to ~$1,400.

The ceiling was still there. Vercel's pricing model compounds with growth. The better your product does, the more you pay — at a rate that outpaces any reasonable unit economics for an early SaaS.

The two options we seriously evaluated

Option 1: VPS + Coolify

Coolify is open-source and self-hostable. You bring a VPS (we looked at Hetzner — €11/month for 4 vCPU, 8GB RAM), install Coolify with one command, and connect your GitHub repo. You get:

• Push-to-deploy (same workflow as Vercel)
• Automatic SSL via Let's Encrypt
• Environment variable management
• Preview deployments

Total monthly cost: ~$25-40 depending on VPS tier.

The trade-off: you own the server. Downtime at 2am is your problem. For a small team that's a real consideration.

Option 2: AWS Lambda directly (what we chose)

We used OpenNext (open-source adapter for Next.js on Lambda) + SST v3 for infrastructure-as-code. Stack looks like this:

Next.js -> OpenNext adapter -> Lambda functions per route
Static assets -> S3 -> CloudFront
DNS: Route 53 + ACM (free SSL)
CI/CD: GitHub Actions -> AWS via OIDC (no long-lived keys)

First month bill: $67.

Lambda's free tier covers 1M requests and 400k GB-seconds of compute per month, forever. Beyond that you're paying fractions of a cent per invocation.

The part everyone skips: testing before you cut over

This is where most migration posts end and most migrations fail.

What we did before touching DNS:

1. Full staging environment on the new infra — identical to prod
2. Smoke tests on every critical path (auth, billing, API routes)
3. Compared every single process.env variable between Vercel dashboard and new infra. Found 3 missing. One would have broken payments.
4. Measured cold start times at p50 and p95. Set CloudWatch alarms.
5. Load tested at 3x our peak traffic using k6. Lambda scaled fine. Our DB connection pool almost didn't — had to increase it.

DNS cutover protocol we used:

• Set TTL to 60s a day before
• Routed 5% of traffic via Route 53 weighted routing
• Watched error rates for 30 min
• Ramped to 100% over 2 hours
• Kept Vercel live for 48hrs as rollback

Zero downtime. Zero customer-reported issues.

Honest cons of going direct to Lambda

• Cold starts are real. Our p95 went from ~180ms on Vercel to ~340ms after migration. Warming strategies help but add complexity.
• IAM permissions will frustrate you. Budget a day just for this.
• No pretty dashboard. CloudWatch logs are not Vercel logs.
• If something breaks, you're debugging AWS, not submitting a support ticket.

Who should and shouldn't migrate

Stay on Vercel if:

• You're still finding product-market fit
• Your bill is under $100/month
• Nobody on the team has touched AWS before
• You're shipping major features every week

Migrate if:

• Bill is threatening your path to profitability
• Traffic is predictable (not random spike-based)
• You have 1-2 days to invest in the migration
• You're post-PMF and tightening unit economics

TL;DR

Vercel: best DX in the business, pricing punishes growth. $1,800/mo -> $67/mo by going direct to Lambda with OpenNext + SST. Migration took a weekend. QA took longer than the deployment.

If you're evaluating the same decision, happy to answer specifics in the comments — stack, bill amounts, traffic numbers, whatever helps.

Stack: Next.js 14, Lambda via OpenNext, SST v3, Hetzner (for staging), GitHub Actions, Route 53, CloudFront, RDS PostgreSQL.