Tessera

Quick poll 👇 Do you use feature flags in production? 🟢 Yes, all the time 🟡 Sometimes 🔴 Rarely ⚫️ Never Reply with why. I’m genuinely curious what’s stopping most people.

Pro tip for fullstack devs: Use feature flags not just for releases, but for: - Gradual rollouts - User targeting - Dark launches - Quick kill switches Changes how confidently you can ship. What’s one use case you haven’t tried yet?

Hot take: You don’t need a massive feature flag platform to get 80% of the value. Unlimited flags, clean SDKs, instant rollbacks, and usage-based pricing is usually enough for most teams. That’s what we’re focused on with Basestack.

Start with kill switches. The first feature flag most teams should add is one that can instantly disable a risky feature in production. Saved us multiple times already. What would be your first feature flag if you added one today?

Quick question: How do you currently handle forms in your projects? A) Custom backend B) Third-party service C) Still copy-pasting old code Reply with your setup. Curious what most people are using.

Most form tools either feel too basic or too expensive once you scale. We built Basestack Forms to sit in the middle Unlimited forms + submissions, spam protection, webhooks, and a clean dashboard. All while staying simple to set up. What’s missing in your current form tool?

Teams support in both Feature Flags and Forms. Invite people, set permissions per project, and still only pay for what you use. Been using it internally and it already removed a lot of friction. Small but useful win this week.

Quick poll for devs building products: Reply with your biggest blocker or success story. I’ll share what’s worked for us.

Dogfooding your own tools is the fastest way to find real problems. We’ve been using Basestack Flags and Forms while building Basestack. Found multiple UX and edge case issues we would’ve missed otherwise. Highly recommend it if you’re building dev tools.

Tired of full redeploys just to test one new feature with beta users? We can now: • Deploy code safely • One-click rollback if anything looks off • Run real experiments without extra tools What’s one feature you’ve delayed shipping because of deployment risk? 👇

Hydration helpers in the Basestack React SDK. No more flash of wrong UI when using feature flags with Next.js Server Components. Took a couple tries to get right, but the DX feels much better now. If you’re using React + feature flags, this should help.

Spam protection on forms shouldn’t require extra services. With Basestack Forms you get built-in spam filtering + clean submission logs out of the box. Point your form at our endpoint and you’re done. Anyone else tired of spam in their form submissions?

I used to hate shipping new features. One bad deploy = rollback stress + support tickets. Then we started using feature flags the right way. Here’s the exact approach that let us move much faster (and sleep better) while building Basestack 🧵

That Friday afternoon deploy feeling… You merge, cross your fingers, and spend the weekend checking logs. Feature flags turned this into “ship it behind a flag and enable Monday”. Huge difference in stress levels. Anyone else still deploying without safety nets?

Remote config is one of the most underrated parts of feature flags. Change text, limits, or behavior in production without touching code or deploying. We use it constantly while building Basestack. What value in your app would you love to update instantly?

Feature flags let you deploy code without releasing it. Ship on Monday, enable for your team on Tuesday, roll out to users on Thursday. No more “let’s hope this deploy doesn’t break anything” energy. What feature are you currently scared to ship?

Remote config via feature flags is underrated. Instead of redeploying for every small change, you can update behavior instantly. We use this for things like: - A/B test variants What’s one setting in your app you wish you could change without deploying?

Quick poll for devs 👇 Reply with your biggest headache. I’ll share what worked for us. (We’re building exactly for this at Basestack)

Tired of risky deployments and messy form backends? Here's how we fixed both in one platform. 🧵

That moment when you ship a “small feature” and something breaks in prod at 2am… Feature flags + remote config would have let us toggle it off instantly. We dogfood this heavily while building Basestack.

Feature flags vs long-lived branches: Why fight merge hell when you can control releases remotely? Basestack vs traditional CI/CD pain.

Startup founder mode: Launch a new checkout feature to beta users only. Roll it back instantly when bugs appear. That's @basestack_co Feature Flags in action. Perfect for indie hackers and growing teams.

Quick tip for solo devs: Stop losing leads to broken contact forms. Point your form action to @basestack_co and get a full dashboard + spam protection. Takes 2 minutes. No server needed. basestack.co/product/forms