pretix
Registration and ticket sales for coworking workshops and events
Review status: Research backlog. Research candidate with incomplete checks; not a vetted recommendation.
Official Website · Source Code
oss-osi-approved planned guideOverview
pretix provides event ticket shops and registration management. A coworking operator could sell workshop tickets and organize check-in for community or venue events, while staff own capacity, refunds and tax decisions. Self-hosted Community, commercial Enterprise and paid Hosted offerings have different support and feature conditions.
At a glance
| Field | Value |
|---|---|
| Categories | event-management |
| Deployment | self-hosted, managed-saas |
| License class | oss-osi-approved (AGPL-3.0-only) |
| Cost model | free-self-hosted |
| Implementation difficulty | hard |
| Maintenance burden | high |
| Maturity | stable |
| Freshness status | partially-verified (2026-10-23) |
| Completeness | partial |
| Confidence | medium |
| Directory tier | research-backlog |
Cost reality
Community self-hosting requires server administration, backups and payment-provider fees. Hosted charges ticket fees plus payment processing, with a quota for free tickets; Enterprise, support and some modules are commercial.
Plans, provider terms and prices change; check official sources before making a budget or deployment decision.
Tasks reduced or augmented
Software does not replace community or ops staff. It may reduce or augment:
- Collect workshop registrations and issue event tickets
- Maintain order and attendee lists for event staff
Human oversight still needed
- Approve event capacity, taxes, refunds and organizer terms
- Handle payment exceptions and check-in disputes with a manual fallback
Manual process this can replace
Structured task-fit review has not been completed for this tool. Treat the free-text examples above as evaluation prompts, not replacement claims.
Data held
-
attendee contact details
-
registration answers
-
orders and payment references
-
ticket and check-in records
-
Personal data: yes
-
Payment data: yes / possible
Orders and payment references can be personal data. Actual card-data handling depends on provider and configuration and was not tested.
Risks
| Area | Notes |
|---|---|
| Vendor lock-in | Export, migration and restore behavior have not been tested; retain a practical manual fallback before depending on the tool. |
| Security | Protect organizer credentials, payment keys, attendee exports and scanner access. Follow stable-release upgrade guidance and test backup restoration before public sales. |
| Compliance | Staff retain responsibility for taxes, cancellation terms, accessibility and attendee privacy; ticketing software does not establish legal venue capacity. |
| Licensing | Most code uses AGPL v3 with additional terms including attribution and a conditional remote-network exception. Other components have different licenses. Read the full terms before modifying, white-labeling or offering services for third-party organizers. |
| Operational | Use a supported stable release rather than assuming the development branch is a production version. Verify plugins, scanner hardware, payment provider and required commercial modules separately. |
Coworking fit
Roles: event-coordinator, community-manager, finance, technical-operator
Workflows: event-lifecycle
Problems: run-events, reduce-manual-admin
Smallest useful experiment
Create a private ten-person workshop, issue staff test tickets, exercise cancellation and check-in, and reconcile an approved test payment/refund before selling public tickets.
Links
- Homepage
- Repository
- Documentation
- Official website
- Source repository
- Official documentation
- Pricing and edition terms
Implementation guide
No implementation guide is published yet.
Verification
- Status:
partially-verified - Completeness:
partial - Confidence:
medium - Tier:
research-backlog - Last reviewed:
2026-10-23 - Sources:
Bounded official-source metadata review only. Features and edition boundaries were read; installation, task-fit evaluation, operator outcomes, integrations, security and recovery were not tested. Retained in Research Backlog; not a recommendation.