What this FAQ covers
This page answers recurring questions about pricing and billing for website owners, agencies, and technical teams. The answers define practical boundaries, identify the evidence that matters, and explain when a question requires account-specific, technical, contractual, or legal review.
- Can I use Asuruas without a payment card?
- What changes on a paid plan?
- How do browser-page limits differ from audited-page limits?
- Can I pay annually?
Use the answers responsibly
Apply each answer to the actual website, scope, agreement, and evidence. Avoid splitting evidence and decisions across disconnected tools and conversations. When the decision could affect production availability, security, accessibility, billing, privacy, or contractual commitments, document the responsible reviewer and verification plan.
Expand the reach of Pricing and billing
Search visibility and user value improve when pricing and billing answers the real questions people bring to the page. For website owners, agencies, and technical teams, that means covering the decision context, observable signals, implementation boundaries, and proof that the result works in production—not repeating a keyword or publishing a longer version of the same incomplete explanation.
Use the page as part of a connected topic cluster. Link the broad concept to focused implementation guides, definitions, checklists, examples, and the Asuruas workflow that can identify affected URLs. The goal is to help a reader move from discovery to a confident next action while giving search systems clear entities, relationships, and page purpose.
- Inspect authorized scope and accountable owners.
- Inspect dependencies, approvals, and release references.
- Inspect service limits and entitlement boundaries.
- Inspect closure evidence and next review triggers.
Strengthen the answer
Surface the next decision instead of every available module.
Build the topic cluster
Standardize handoff and acceptance criteria.
Prove the outcome
Use retained evidence to improve the next operating cycle.
Questions and answers
01Can I use Asuruas without a payment card?
Yes. Explorer does not require a payment card and includes one verified website, up to 250 audited pages each month, interactive results, remediation tickets, and the implementation library.
02What changes on a paid plan?
Paid plans add websites, monthly page capacity, rendered-browser capacity, longer history, scheduled audits, PDFs, exports, team access, client workspaces, APIs, webhooks, approvals, and portfolio controls according to the selected plan.
03How do browser-page limits differ from audited-page limits?
Audited pages cover the crawler and page-analysis allowance. Rendered-browser pages use a browser worker to inspect JavaScript-dependent output and consume a separate plan allowance.
04Can I pay annually?
Yes for standard paid plans when annual Stripe prices are configured. Annual billing costs ten months of the equivalent monthly plan, and the complete amount is shown before Checkout.
05How are limits applied?
Limits apply across the organization workspace and are checked by the server when a user creates websites, audits, browser runs, invitations, exports, or other entitled resources.
06What happens when a limit is reached?
Existing records remain available where practical, while creation of additional resources may pause until the usage period resets or the plan changes.
07Can I upgrade or cancel?
Authorized billing users can use the Stripe billing portal when enabled. Renewal, cancellation, downgrade, and refund behavior follows the checkout record, published policies, and any signed order.
08When should I contact sales?
Contact sales for managed audits, agency onboarding, custom scale, authenticated scope, SSO, retention, integrations, procurement, security review, onboarding, or service commitments not included in a standard plan.
Turn pricing and billing into an accountable record.
A clear, supportable answer set for pricing and billing linked to the relevant workflow or policy.