Frequently asked questions
Answers to the questions that matter before getting started.
Short, clear, and without filler. This page covers the points people usually want to understand before signing up, testing the product, or upgrading.
Product and access
Can I try the product before paying?+
Yes. The onboarding path is intentionally lightweight so you can evaluate the product in a real workflow before an upgrade becomes relevant.
Do I need a team or multiple users right away?+
No. You can start solo and invite more people later once your workflow is stable or collaboration actually matters.
Can I upgrade to a paid plan later?+
Yes. The upgrade path is designed to stay simple so you only pay once usage becomes regular or you need higher limits.
Billing and privacy
What happens to my data if I cancel?+
Access and data handling should stay predictable. The legal details are covered in the privacy policy and terms linked in the footer.
Will I be charged if I barely use the product?+
The product is structured around a clear free-to-upgrade path so costs should only appear once the value and usage justify them.
Is Stripe required for payments?+
For real billing, yes. During development, billing can still run in mock mode so product work is not blocked by early Stripe setup.
Technical setup
Do I need my own database in production?+
Yes. The app runs separately from the database. In production you connect an external Postgres database, while locally you can use Docker or a hosted test database.
Is this better suited for MVPs or real customers?+
Both. The setup is lean enough for fast validation, but structured enough to keep evolving into a real SaaS used by actual customers.
How quickly can I get into the dashboard?+
As soon as your account exists, you can move straight into the protected area. Navigation and data loading are designed to keep that path smooth.