Gymlocity (https://gymlocity.com) - All-in-one gym management platform for small gym owners.

Building this for personal trainers with home gyms and small 1-2 location owner-operated facilities. The big players (Mindbody, etc.) are overkill and expensive for this market.

Core features: class scheduling, member booking, Stripe payments, and workout programming (the part most gym software ignores - trainers still use spreadsheets or generic apps).

Stack: React 19 + Vite frontend, ASP.NET Core 10 API, PostgreSQL, multi-tenant architecture so each gym gets their own branded experience.

Currently polishing the member dashboard and workout tracking UI. The goal is something a solo trainer can set up in an afternoon without needing to call sales or sit through demos.

I’ve had decent results with this for context management in large code bases so far https://github.com/GMaN1911/claude-cognitive

Solid platform - clean and useful for algorithm practice.

Quick suggestions:

  - GitHub OAuth would feel natural for devs.
  - Broaden language support (C#, TypeScript, Ruby).
  - Add dark/light mode toggle for comfort.

Excited to see where it goes — thanks for building.

In a cold climate, I would expect burying it to use the ground as a natural insulator. Why was an above ground design chosen?

Specifically, does the need for heavy insulation and the active heating of the sand make the ground a less effective or even problematic insulator? Could excavating and building a below-ground foundation for a high-temperature device like this be more complex and expensive than an above-ground silo? How would permafrost conditions affect this design?

It seems that this is directional, flowing from Android to Apple but not necessarily back (e.g., me airdropping a photo to my parent who uses Android). I'd love for this to work in the other direction as well.

I’m building https://www.kidcarekit.com, a Rails SaaS for family-run daycare centers that still juggle spreadsheets and phone calls. It wraps waitlist management, enrollments, and Stripe billing into a single dashboard with Tailwind + Hotwire on the front, Devise for auth, and Azure Blob for logos. Solid Queue handles scheduled jobs like weekly tuition and late fee automation so owners get predictable cash flow without hand-cranking invoices, while MailerSend keeps parents in the loop.

Right now I’m polishing the onboarding flow so new centers can import families, configure their billing cadence, and connect Stripe in under ten minutes. Next up is richer analytics (occupancy tracking and revenue health) and rolling out a guided setup for late fee policies. If you’re running childcare ops or know someone who is, I’d love feedback on the workflow pain points you still feel daily.