Accounts & access
Email sign-in, recovery and protected sessions. OAuth and passkeys need provider and browser acceptance.
Read the guide ↗Useful pieces.
Clear boundaries.
Reuse the everyday infrastructure. Own the behavior that makes your product different.
Local-ready means verified locally. Integration pending means the code is present but external acceptance remains. Planned modules are not available yet.
Teams & organizations
Create and switch teams, manage members and invitations. Actual invitation delivery remains unverified.
Read the guide ↗Subscriptions
Stripe checkout and portal integration, gated by complete credentials. Real payments and webhooks remain to be verified.
Read the guide ↗Credits & history
User-scoped results, export and an atomic credit ledger. Credit-pack flows exist locally; real payments remain to be verified. Example browser tools are free.
Read the guide ↗Content & discovery
Static task pages and Markdown articles with canonical URLs, structured data, sitemaps and RSS.
Read the guide ↗A reusable interface
Astryx, StyleX and shared matte black and white tokens, with accessible controls and responsive navigation.
Read the guide ↗Independent projects
Generate a clean product project with its own brand, configuration and preview. Keep your custom product code in your own repository.
Read the guide ↗Edge deployment
Cloudflare Workers and Neon configuration with internal service bindings. Production deployment has not been accepted yet.
Read the guide ↗Files & background jobs
Private files, queues and retry-aware local task processing. Real storage and model acceptance remain for a later stage.
Read the guide ↗