Vitor Amaral

As a user who's been with the Arc browser almost since the beginning, this is a pretty shitty decision, it just goes to show that the browser company shot itself in the foot. They thought everyone would switch to Dia, but instead people stuck with Arc, and now the only option is to shut down Arc.

Introducing Basestack Feature Flags 2.0 🚀 🚀 This release brings some big improvements to our feature flags product! ✨ New master details page 💬 Comments & follows 📊 Improved activity log 👀 Feature previews 🔗 Code references Check out the thread below 👇

View full thread

🔗 Code references 🧹 Time to clean up your codebase, but not sure where to start with feature flags? Use our CLI to sync your codebase with the Basestack dashboard, then leverage code references to find where flags are used and identify unused flags ready for cleanup.

basestack.coBasestack Feature Flags: Progressive Delivery PlatformRelease safely with Basestack Feature Flags. Roll out gradually, target segments, and manage environments with full audit history.

Learn more at basestack.co/product/feat...

📊 Improved activity log 📋 We’ve upgraded the activity log for feature flags! Now you can track everything in one place from deletions and flag name changes to comments and more. Full visibility. Every change. One activity log. 🔍

👀 Feature previews 🚀 Not quite ready to roll out a feature? Use Feature Preview to let users opt in, gather early feedback, and improve your product before the full release. Ship with confidence. Build with your users. 💡

💬 Comments & follows Follow feature flag releases and discuss changes with your teammates right from the flag details page. 💬 Stay in the loop with notifications about updates and critical changes. 🔔

15 Sept

he Files page is the hub for files uploaded with your submissions. Each submission still has its own files. This page gives you the overview.

basestack.coBasestack Forms: Form Backend and APIs for DevelopersCreate production-ready forms with spam protection, flexible integrations, and developer-friendly APIs using Basestack Forms.

15 Sept

Learn more at basestack.co/product/forms

Introducing Basestack Forms 2.0 🚀 This release lets you upload files on any form and set submission rules for tighter control and security. Read the posts below for the details.

This release also adds a new Flow page, where you can see your form’s full workflow. We’re also introducing Rules: security checks that block malicious or invalid submissions. You define the structure your form must follow; anything that doesn’t match is rejected.

Here are some quick links to get started: Landing Page: basestack.co/product/forms Dashboard: forms.basestack.co Docs: docs.basestack.co/content/forms

Introducing Basestack Forms 2.0 🚀 This release lets you upload files on any form and set submission rules for tighter control and security. Read the posts below for the details.

Each form now has its own Files section. Upload common file types, then delete, download, or manage every file submitted through that form, all in one place. File uploads are off by default. Enable them in each form’s settings; otherwise, submissions with files are rejected.

The Files page lists every upload, but each file still belongs to its submission. Open a submission to see exactly which files were attached.

10 Aug

Organizing feature flags by project just hits different 🔥 One clean card. Every environment (dev → staging → prod) right there in a single view. No tab-hopping. No guessing. Instant control. That’s how progressive delivery should feel.

basestack.coBasestack Feature Flags: Progressive Delivery PlatformRelease safely with Basestack Feature Flags. Roll out gradually, target segments, and manage environments with full audit history.

10 Aug

Learn more basestack.co/product/feat...

18 July

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.

17 July

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?

16 July

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.

15 July

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?

14 July

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.

14 July

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?

13 July

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.

13 July

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

12 July

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.

12 July

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? 👇

11 July

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.

11 July

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 🧵

Biggest lessons so far: - Start with kill switches for risky features - Use descriptive flag names + clean up old ones - Don’t over-engineer early This is how modern teams (and smart indie devs) ship confidently.

If you want to try the same tools we use → basestack.co/product/feat... What’s your current release process like? Any war stories? 👇

We wanted to test a new bulk export feature. Instead of deploying and hoping: 1. Created flag “bulk-export-v2” 2. Deployed code (flag off) 3. One-click rollback when we spotted an edge case 4. Fixed → enabled for more users Zero downtime. Zero angry users.

How to start (works with any stack): Use something lightweight like Basestack Feature Flags. We have SDKs for vanilla JS and React. Basic flow: - Init client with your project + environment key - Check flag value - Conditionally render or run logic Took us under 30 lines

Old way (painful): - Build feature - Deploy to prod - Cross fingers - If broken → emergency deploy or revert New way (with flags): - Build feature behind a flag - Deploy anytime safely - Monitor + instant rollback if needed Deploy ≠ Release anymore.

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?

9 July

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?

7 July

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. 🧵

We’re on a mission to help product teams build faster and launch smarter. Forms + Feature Flags (Feedback tool coming soon) all in one stack. Ready to try it? → basestack.co

What’s your biggest bottleneck right now? A) Forms & backend B) Safe feature releases C) Collecting user feedback Reply below 👇 I read every comment. Let’s talk tools! #BuildInPublic #IndieHackers #SaaS

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

Why teams & indie hackers love it: - Launch faster (no more "hope it works" deploys) - Reduce risk dramatically - Perfect for A/B testing, beta features, kill switches - Scales from solo dev → startup → enterprise

Basestack highlights: • Simple & clean dashboard • Transparent pay-as-you-go pricing ($5 credit to start) • Built for developers who hate complexity

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

Real example: A marketer collects leads → automatic thank-you page → data lands in Basestack → export to your CRM. All with HTML or JavaScript. Takes < 5 minutes.

Problem #2: Feature Flags You want to test in production safely, but branching + redeploying is painful. Basestack Feature Flags lets you: • Toggle features for specific users/environments • Activity history • SDKs for JS/React + API • Remote config without redeploys

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

Most devs waste hours on: - Setting up form endpoints - Server-side code just for submissions - Scary feature releases that can break production What if you could solve both with one developer-first platform? Meet Basestack → basestack.co

Problem #1: Forms You build a beautiful lead/survey form… then spend a weekend wiring up a backend. Basestack Forms fixes this: • Just point your <form> action to our endpoint (no server needed) • Spam protection + email notifications • Dashboard to manage everything

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.