Authentication
DynexisAI uses Clerk for account authentication and protected dashboard access.
Signed-in workspaceProtected dashboard routesAccount-linked usage
Security and trust
Practical safeguards for the current DynexisAI MVP.
DynexisAI is early, so trust is handled plainly: protect accounts, use trusted providers for auth and billing, keep private keys on the server, and improve controls as real usage grows.
Current trust posture
Secure the MVP first.
Server-side route handlers keep private API keys out of the browser.
Stripe is used for billing so payment handling stays with a dedicated provider.
Admin and dashboard routes are separated from public marketing pages.
Robots rules block public indexing of admin, API, dashboard, and auth routes.
Payments
Stripe handles checkout and subscription billing. DynexisAI does not store full card numbers.
Stripe checkoutCustomer portalSubscription webhooks
Saved work
Projects and documents are designed to be tied to user accounts so work stays organized and recoverable.
Saved projectsUser ownershipWorkspace history
Usage control
Free and Pro usage limits help protect product quality and manage AI costs responsibly.
Monthly limitsPlan awarenessAdmin visibility
Trust roadmap
Security grows with the product.
The current focus is a secure MVP. Formal enterprise controls, certifications, and deeper governance should come after user validation and product maturity.
1
Clearer controls for saved projects and documents.
2
More detailed usage and support review tools.
3
Expanded security documentation as the user base grows.
4
Additional compliance work after MVP validation and customer demand.
Have a security question?
Contact DynexisAI with questions about accounts, billing, saved projects, or AI data handling.