Teamspective - AI Leadership Enablement & People Analytics Platform Empower every leader with AI-guided insights, engagement analytics, and actionable feedback. Improve performance, collaboration, and culture across your organization.

At teamspective.com we replaced months of UI work with a chat box. Combining data across products used to mean clicking through dashboards. Now it's one message

Building good UI is really hard. Chat buys time to figure out what it actually needs to be. Not the end state, but way better than rushing dashboards nobody wants to use

#buildinpublic #webdev

My server is in Finland, run by a German company. No US jurisdiction over my data. That wasn't why I moved, but it's something I've started paying more attention to.

Anyone else self-hosting? Where do you draw the line between convenience and control?

NixOS and Kubernetes configs were mostly vibe coded with Claude. Took a weekend.

Now I modify my infra from my phone. Prompt Claude, it opens a PR, I preview, I merge. No dashboards. Vibe infrastructure. And the cost stays at 8€ no matter how much I deploy.

On Fly.io, Render, or Railway a single always-on service runs roughly 5-7€. But a real app is never one container.
My sync engine powered app needs the app, a sync server, and Postgres. Three services, 15-20€ for one project. I run all that plus other apps on Hetzner for 8€ total.

I moved all my personal projects off Vercel to a self-hosted Hetzner server

Free tiers are great for hobby projects. But the moment you need long-running processes, you're paying. A sync engine, a 24/7 data collector, Postgres. These aren't serverless workloads.

#buildinpublic #selfhosting #webdev

Still looking for more interviews across all three groups. If this sounds like you, DM me - or just reply with what you're building, I'd love to hear about it

#buildinpublic

I've been interviewing practitioners across the space: engine builders, engineers using sync engines in production, and teams that built custom

This has been really helpful for my MSc thesis research at Aalto University (@aalto.fi). I'm exploring sync engine architectures: when off-the-shelf sync works well and when teams end up building custom

#localfirst #webdev

This shouldn't surprise me. I notice this pattern in myself too - if I find some cool tech, I'll share it with colleagues and friends

SWEs really love talking about their tech stack, especially if it involves sync or local-first

Our caching strategy is "hope two people don't edit the same thing at once." Low concurrency has been carrying the entire stack for years. Now more users and larger orgs are jumping in and the cracks are starting to show.

What kind of planning?

Home-Cooked Software and Barefoot Developers The emerging golden age of home-cooked software, barefoot developers, and why the local-first community should help build it

Full talk + transcript here: maggieappleton.com/home-cooked-...

Want to try out sweepmail.app, the email experience for indie hackers, solopreneurs and founders? Join the waitlist at sweepmail.app 🧹

Just watched @maggieappleton.com's talk on home-cooked software and it really clicked with what I'm doing with sweepmail.app! 🎯

Makes sense that not every piece of software needs to scale to millions of users

🛠️ #buildinpublic #webdev #indiehacker

Sweepmail - Reach Inbox Zero with Blazing Fast Email Automation Powerful shortcuts and intelligent rules transform your inbox. Stay focused on what matters.

I just launched a waitlist for sweepmail.app! ✨🧹

Google Cloud allows me to invite up to 100 test users. I will let some people test the app in the next few weeks once the core functionality is in place!

#buildinpublic #indiehacker #productivity #webdev

Thanks Roope! Launch week coming 🙌🔥

No public link yet, since the Google app would require verification for that. I could grant access to specific test user emails at a later stage if people want to try it out!

I used @tanstack.com Query with indexeddb to make the app fast as heck. Next steps to figure out a smart way to prefetch the emails since the Gmail listing API only has IDs by default.

If it even makes sense to do this without any server storage...

#svelte #typescript #webdev

Screenshot of a work in progress web application showing an email with text content only and a JSON block below that with the email in raw format

I just built a toy version of my Gmail client for mysidequest.xyz Week 3!

It has working OAuth and connection to the Gmail API. Only text render at this point, but I learned a lot about parsing the email format. I even got åöä to work properly 🙌

#webdev #sidequest #buildinpublic

I will experiment with many things, but presume the core would be: super fast client, keyboard shortcuts for everything, auto-triage and tagging! Thanks for the feedback

Awesome! Looking forward to future updates to keep you posted

Zero clicks, zero unread emails Blazing shortcuts and smart rules run your email inbox on autopilot. Lets founders focus on what matters: ship fast and talk to customers—not on unread emails. project index, sidequest

I am building a side project with mysidequest.xyz! My goal for the program is to have a functioning email client that I can personally use instead of sluggish Gmail by the end of 6 weeks. Planning to post progress updates here every week!

#svelte #local-first #gmail

Hey bsky! Never became active on Twitter, but this seems like a new start 👋

Interested in all things web dev. Recently dove into the world of local-first thanks to @syntax.fm and @localfirst.fm. Looking to found a startup at some point in the near future 🏗️