SoloBoss
Complete platform for freelancers and small business owners
Visit Website
February 15, 2026
Just launched SoloBoss — an operating system for solo businesses
I built SoloBoss because most freelancers and solo operators are duct-taping 5–10 tools together just to run a simple business.
Invoices in one app. Tasks in another. Notes somewhere else. Payments somewhere else.
SoloBoss puts everything in one place:
• Clients
• Tasks
• Notes
• Payments
• Revenue tracking
Simple, clean, and built for people running a business alone.
It’s early, live, and I’m looking for real feedback from freelancers, developers, and solo operators.
If you run a one-person business, I’d genuinely love to know:
What’s the most annoying part of managing your work right now?
Try it: https://soloboss.app
3 Comments
Nice idea. When client records, invoices, and payments live in the same system, cross-tenant access control becomes critical. Are you validating object-level authorization on invoice and client endpoints?
Yes — every table enforces object-level authorization via row-level security policies scoped to auth.uid(). No API endpoint can return or mutate another tenant's data, even with a valid session. Nested resources (line items, attachments) verify ownership through parent record joins. Edge functions validate JWTs server-side before any data access.
That’s a strong setup. Row-level security scoped to auth.uid() plus parent record joins for nested resources is the right pattern.
Good call validating JWTs server-side before any data access. That closes a lot of common gaps.
We’re the Nautillo Pro team. We focus heavily on SaaS security, which is why we ask these questions. We simulate real attacker paths to see whether object-level authorization still holds under chaining and edge cases.
If you ever want an external check on those boundaries, we offer a free version you can run periodically.