Find answers, support paths, and rollout guidance fast
Search the same approved public knowledge source used by AwraIQ. Results stay grounded in published AWRA resources, so buyers, customers, and support teams work from one source of truth.
Product helpImplementationSecurity reviewsBilling & support
Every module AWRA OpsHub ships, with a screenshot, its feature pages and what each plan includes. The plan columns are read from the same plan rules the app enforces: the free trial opens every module, and Basic, Pro, Premium and Enterprise each show included, core or view-only access per module.
All rights reserved means AWRA keeps ownership and control over its protected intellectual property except where AWRA grants rights through law, public guidance, an open license, a customer agreement, a partner agreement, or a separate written approval.
Open-source modular ERP Open-source modular ERP AWRA OpsHub vs open-source modular ERP Powerful and endlessly configurable — once someone configures it. Open-source modular ERPs are genuinely capable, with a module for almost everything.
A dunning ladder sends a friendly note, then a firm one, then a final notice, then tells your team — by email, SMS and WhatsApp, in your words, with a link to pay. Each stage goes out once, payment stops it, and a customer you are talking to can be paused.
Spreadsheets, a stack of separate apps, a traditional ERP, or AWRA OpsHub. Each one is right for somebody. This page sets out where each fits, where each breaks, and the systems AWRA should run alongside rather than try to replace.
Your own AWRA OpsHub, used by your organization alone at your own address — the one-sentence answer for donors, boards and regulators who ask where your data lives. Hosted, updated and backed up by us.
Only an organization administrator or owner can delete the organization. If you are an individual user who is not an administrator, contact your organization administrator, or use Option 2 below to reach us.
Every other module answers “what happened”. Operations Hub answers “what needs me today” — pulling the same records the rest of the platform already holds into five screens built for deciding rather than browsing.
A sub-processor is a vetted third party that may process personal data on your behalf so we can run the platform. We stay responsible to you for each one. These are the commitments behind every name on this page.
Your own system, used by your organization and nobody else, at an address with your name on it. All the confidence of running your own, with none of the servers, upgrades or backups — those stay with us.
These Partner Program Terms & Conditions (the "Partner Terms" govern your participation in the AWRA OpsHub Partner Program (the "Program" operated by AWRA OpsHub ("AWRA", "we", "us", or "our").
The AWRA OpsHub funding presentation: the US$10K seed round, what it funds — product hardening, owned infrastructure and go-to-market — and the platform behind it.
A living view of where AWRA OpsHub is headed — what's planned, in active build, and just shipped. Filter by area, then vote to push the ideas your team needs to the top.
Everything journalists, analysts and partners need to write about AWRA OpsHub — company facts, the latest product news, boilerplate copy and a downloadable media kit.
AWRA OpsHub was born from real operational friction and a belief that organizations deserve one intelligent platform for the work that keeps them moving.
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.
We use necessary cookies for secure sessions. With your permission, we also use cookies and browser storage for preferences, analytics, and demo engagement. Privacy Policy
AWRA OpsHub
Cookie settings
Cookie Consent Manager
Necessary cookies stay on for login, CSRF protection, and security. You can choose the optional categories below.
Overview
General Information
AWRA uses cookies and browser storage to keep public pages secure, remember selected preferences, measure website performance, and manage demo engagement prompts.
You can choose whether functional and marketing engagement storage apply. Analytics measurement is always active in this AWRA setup.
These settings apply to AWRA public website experiences such as the homepage, feature pages, pricing calculator, blog, help center, and request-demo page. Authenticated dashboard and vendor portal sessions still rely on required security cookies.
Required
Always active
Functional
Optional
Analytics
Always active
Marketing
Optional
For more context on privacy handling, open the Privacy Policy.
Required Cookies
Required Cookies
Always Active
Required cookies and storage support basic website delivery, secure sessions, request protection, and remembering the consent choice itself.
These cannot be switched off from this manager because disabling them would break login/session behavior, form protection, or the ability to remember the privacy choice you save.
Cookie details
Session security: keeps secure server sessions working while browsing AWRA.
CSRF protection: helps verify form submissions and protect requests.
Consent record: stores the preference decision so the banner does not keep asking after a choice is saved.
Examples: Laravel session cookies, CSRF tokens, and the AWRA consent preference record.
Duration: session security can expire with the browser/session; saved consent can last longer so the same browser remembers the choice.
Functional Cookies
Functional Cookies
Functional storage improves the public website experience by remembering interface choices, helper states, dismissed notices, and short-lived interaction preferences.
Turning this off does not stop secure required cookies or analytics. It only limits optional convenience memory.
If disabled, AWRA may show some helper prompts again or forget non-essential display choices. Core public pages, contact forms, and request-demo forms still work.
Cookie details
UI preferences: remembered display choices and helper states where available.
Dismissed notices: session-level or preference-level memory for notices the visitor has closed.
Frequency helpers: optional browser storage that prevents repeated prompts when allowed.
Examples: localStorage or sessionStorage values for dismissed banners, guide/helper states, and lightweight public-page preferences.
Effect when off: AWRA avoids optional convenience memory unless it is also allowed through marketing and engagement preferences.
Analytics Cookies
Analytics Cookies
Always Active
Analytics helps AWRA understand public page performance, traffic patterns, and content usefulness so we can improve the marketing website.
This category does not by itself enable demo popups, exit-intent prompts, or advertising pixels. Those are controlled by Marketing & engagement.
In this AWRA setup, Google Analytics and Google Tag Manager measurement are treated as mandatory website measurement and remain active.
Cookie details
Google Analytics / GTM: measures aggregate traffic and page activity.
Performance insight: helps identify which public pages, docs, and demo paths visitors use.
Operational signal: supports website quality decisions without enabling demo popups by itself.
Examples: Google measurement identifiers such as GA/GTM tags and related browser identifiers set by Google scripts.
Use: page views, source/referrer trends, public content performance, and product education page effectiveness.
Marketing & engagement
Marketing & engagement
Marketing and engagement storage supports demo prompts, exit-intent prompts, campaign attribution, and future advertising pixels.
When disabled, AWRA will not auto-open demo or exit-intent popups. CTA buttons can still open a form because that is a direct visitor action.
When enabled, AWRA can remember that a visitor already saw, dismissed, or submitted a demo prompt so the same popup is not repeated aggressively.
Cookie details
Demo prompt memory: tracks whether an auto prompt or exit prompt was recently dismissed.
Demo submission memory: avoids asking again after a visitor submits a demo request.
Campaign context: keeps source page, referrer, and UTM context available for demo requests.
Examples: popup frequency caps, demo-submitted flags, engagement source fields, and UTM/referrer context.
Effect when off: auto demo prompts and exit-intent prompts stay blocked; normal navigation and manually clicked CTA buttons still work.