Security operations for teams that take accounts seriously.
Manage licenses, run consented security checks, bill teams and sell digital goods from one coherent platform. Persistent data, server-side authorization, audited actions.
No credit card required to explore the platform.
Authorized job
Illustrative — not live tenant data.
- REQUESTED
- CONSENT_PENDING
- AUTHORIZED
- QUEUED
- RUNNINGrunning
- VERIFYING
- COMPLETED
Consent record required before a job can leave CONSENT_PENDING.
One platform, coherent by design
Shared tokens, shared contracts and one authorization model across the public site, customer portal, API, worker, bot and admin.
Consent-first security checks
Every job requires a documented authorization record. Owners confirm, and the audit trail proves it.
License lifecycle
Day, weekly, monthly, 90-day and annual licenses with a tested state machine: pending, active, grace, expired, suspended, revoked.
Team workspaces
Organizations, invitations and roles — owner, admin, member and read-only — enforced server-side.
Billing you can audit
Checkout, subscriptions, invoices and refunds verified through provider webhooks, never the browser redirect.
Digital marketplace
Inventory, server-side pricing, idempotent orders and delivery only after confirmed payment.
Operations center
Real metrics, queue monitoring, feature flags and an audit log for every sensitive admin action.
Security and privacy are the product
Sensitive actions are authorized on the server, recorded in a redacted audit log, and never trusted to client state.
- Argon2id password hashing
- Hashed session and API tokens
- Tenant-scoped reads and writes
- Webhook signature verification
- No full card data stored
- Redacted, structured logs
A workflow you can prove
Every job moves through a tested state machine. Invalid transitions are rejected; interruptions resume without double processing.
Terminal and error states also include FAILED, CANCELLED, REQUIRES_ACTION and EXPIRED.
Starter
For individuals evaluating the platform.
Team
PopularFor teams running regular security workflows.
Frequently asked questions
What exactly does AutoSecure do?
AutoSecure is a platform for authorized account-security workflows, license management and a digital marketplace. It stores persistent business data in PostgreSQL and enforces authorization on the server for every protected action.
Do you scan accounts without permission?
No. Every security job requires a documented consent record tying the subject to the requesting tenant. Without it, a job cannot leave the CONSENT_PENDING state.
How are payments handled?
A payment provider (for example Stripe) handles card data; AutoSecure never stores full card numbers. Licenses and orders are activated only after a verified server-side payment status — not from a browser redirect.
Can I cancel or downgrade?
Yes. Subscriptions can be cancelled or changed; the license keeps a defined grace period before it expires, and the change is recorded in the audit log.
Is the data multi-tenant safe?
Tenant-scoped rows carry an orgId, and every protected read and write is scoped to the caller's membership. Cross-tenant access is covered by dedicated tests.