One core, many modules
Prastix isn’t a bundle of separate products. Every module runs on the same core, so your records, permissions and audit trail are shared rather than copied between systems.
The shared core
The part of Prastix that every module relies on, and that you never have to set up twice.
- Your own database
- Each organisation’s supporters, entries, payments, content and messages live in a database of its own, reached with credentials of its own.
- Staff sign-in
- Your team signs in with Microsoft 365 or Google if you use them, or a Prastix account with two-step verification. Roles decide what each person can see and do.
- Supporter accounts
- Supporters sign in on your website, under your name and brand. They have an account with you, not with Prastix.
- Permissions
- Checked every time something happens, whether it comes from the website, an app, a staff screen or an integration.
- Audit trail
- Every material action records who did it, when, under which permission and what changed.
Modules, not silos
Each module owns its own rules and works with the others through the core.
A payment is only treated as received once your payment provider confirms it. The lottery module then decides whether that makes an entry valid. The members area shows the supporter their entry, and JourneyCheck checks the whole journey works end to end.
Your platform contract decides which modules you can use. Your site managers decide which of those to switch on, site by site. Turning a module off never deletes records you’re legally required to keep: you see what will be affected before you confirm.
What supporters use
- Your website
- Members area
- Branded apps
- Wallet passes
- Free games
What your team runs
- Lottery
- Raffles and prize draws
- Payments and Direct Debit
- Messaging
- Kiply documents
Shared by every module
- Supporter records
- Consent
- Notifications
- Financial journal
- Reporting
The Prastix core
- Your own database
- Staff sign-in and roles
- Permissions
- Audit trail
Designed for phones first, and for everyone
Every public page, form and account screen is designed for a narrow screen first. Everything is built to WCAG 2.2 AA: keyboard navigation, screen readers, zoom and reflow, contrast, captions, reduced motion, and alternatives to time limits.
That includes the parts that are easy to forget. A popup can be closed with the keyboard, a timed quiz offers more time, and a spot-the-difference game has a non-visual alternative.
Lighthouse scores help us catch problems, but we don’t treat them as proof of accessibility. Manual testing with assistive technology is part of every release.
Where it runs
- UK hosting
- The platform and your data run on servers in London. Nothing about your supporters is sent to an AI provider: AI features run on our own servers.
- Backups
- Encrypted every night and stored in the UK, with a second copy held separately so a single failure can’t remove both. We restore backups every month to prove they work.
- Separate environments
- Development and testing run apart from the live platform, with their own data and credentials. Real supporter data isn’t used for testing.