Decide who sees what
You decide where your data lives, who works on it and how changes can be demonstrated.
The starting point
Security means control
Business data is often among the most valuable things a company owns. Whoever entrusts it to a system wants to know three things. Where does the data live, who can reach it, and what happens to it?
In Spice, you answer all three questions yourselves, not your software vendor. The location follows from the form of operation you choose. Access is governed by permissions that you define. What happens is recorded by the system in a traceable way.
This applies equally to SpiceCRM, SpiceHCM and SpiceQMS, because all three share one platform. Know the rules in one product, and you know them in all three.
Finely graded rights, changes on record
Permission profiles and permission objects control access in fine detail, module by module. They distinguish own records from all records, for reading, editing, creating and deleting. People in sales then see only their own accounts and opportunities, while sales management sees all. Each role also gets a navigation of its own, and dashboards follow the profiles too. If someone takes on new tasks, you change the profile, not every single right.
One shared audit trail records changes across all three products. Spice logs access per user. Status networks allow only intended changes, and approvals run through workflows with defined steps. Months later, you can still trace who made a change.
- Adapt permission objects without touching the program code
- Separate profiles for user, role and mailbox administration
- Change history for accounts, contacts and activities
- Sign-in through single sign-on if you wish
Hosting
Your data stays in Europe
You choose: the Spice cloud in EU data centres or your own data centre. Hosting through partner companies is possible, as is moving from the cloud to your premises and back.
Operation
Sovereignty is a choice
Spice offers four forms of operation. The quickest start is the shared Spice cloud. It runs on Google Cloud in European regions.
A dedicated instance in the Spice cloud is yours alone, with its own repository and release cycle. If you want to operate without American companies, run Spice in your own data centre.
The functions are identical in every form. If you run it yourselves, releases arrive with no delay compared to the cloud. Today’s choice does not bind you forever.
Development
Secure from the first line of code
Attacks increasingly begin with flaws in software, not with stolen passwords. That is why security at Spice begins long before operation: in the code itself.
What current studies show
- of data breaches begin with an exploited vulnerability, now the most common way in
- 31%
- new known vulnerabilities in 2025, around 132 a day
- 48,185
- of the commercial codebases examined contain open-source components with known vulnerabilities
- 86%
A data breach now costs USD 4.99 million on average worldwide. Making security a fixed part of development and operations (DevSecOps) is one of the strongest levers for lowering that cost.
Verizon, Data Breach Investigations Report 2026 (opens in a new tab); Jerry Gamblin, 2025 CVE Data Review (National Vulnerability Database data) (opens in a new tab); Black Duck, Open Source Security and Risk Analysis 2025 (opens in a new tab); IBM and Ponemon Institute, Cost of a Data Breach Report 2026 (opens in a new tab)
Testing
Every release is checked before it reaches you
Every release passes mandatory code review and security scans. A finding rated Critical or High stops the build until it is fixed and rescanned.
Code review
Every change is reviewed before it is merged into the main branch.
Code analysis
We analyse the source code statically (static application security testing, SAST) with Semgrep. Its rules follow the Open Worldwide Application Security Project’s list of the most critical web application risks (OWASP Top 10).
Dependencies and containers
Libraries and container images are checked against known vulnerabilities.
Secrets and licences
The code contains no keys or passwords, and the open-source licences are cleared.
Release
A release goes out only when no finding rated Critical or High is open.
Process
Security in every phase
Our development process is set out in a secure development policy and aligned with ISO/IEC 27001. From requirements to maintenance, every phase has a binding security checklist for the development team.
Least privilege
People, services and AI agents receive only the access their task requires.
Strict tenant separation
No company sees another company’s data.
Privacy by design
Data protection under the General Data Protection Regulation (GDPR) is built in from the start, not added later.
Separate environments
Development, test and production environments are kept apart.
No secrets in the code
Passwords, keys and tokens never sit in the source code. Automated scans enforce this.
Trained team
The development team receives regular internal training on current threats to information security.
Vulnerabilities
Fixed deadlines for every finding
All findings are recorded centrally and classified by severity. Each severity has a binding deadline, and every fix is checked again.
Fixed within
- Critical
- 7 days
- High
- 30 days
- Medium
- 90 days
- Low
- 180 days
We inform our customers about vulnerabilities rated Critical by email within 5 days.
Management system
Information security as a system
Our information security management system (ISMS) is aligned with ISO/IEC 27001. It protects the confidentiality, integrity and availability of the data we process, including your customers’ personal data. The Spice cloud runs in ISO/IEC 27001-certified data centres in Europe.
Clear scope
The ISMS covers the software-as-a-service platform and its cloud infrastructure. It also covers the source code repositories, corporate IT, the office and remote work.
Risk-based
The information security officer maintains the risk register and the statement of applicability. Controls follow the assessed risks.
Encrypted
Customer data is encrypted in transit and at rest.
Recovery tested
We check defined recovery time and recovery point objectives (RTO and RPO) with regular restore tests.
Reviewed regularly
Internal audits and management reviews take place regularly, and every policy is reviewed annually.
Frameworks
The ISMS draws on ISO/IEC 27001, the OWASP Application Security Verification Standard (ASVS) and the OWASP Top 10. Data protection follows the GDPR and the Austrian Data Protection Act (DSG).
What changes
Control you can demonstrate
Whoever is responsible for data must account for it to management, regulators and the people concerned. With Spice, you answer such questions from the system, not from memory.
Who may do what is set out in the profiles. What has changed is shown by the audit trail. That spares you searching through emails and spreadsheets when an audit is due.
Write to us with the questions your next audit will ask. We will show you where Spice holds the answers.
More on the architecture
Technology
In the browser, back end via REST, one data model in five layers.
Customisation
No-code, low-code and development in three stages, seven system roles.
Automation
BPMN workflows, reports without code, documents in your own corporate design.
Integrations
REST and SOAP for practically every module, connection to SAP.
Communication
Email, SMS and messenger on the record, telephony and campaigns.
Groupware
Microsoft 365 and Google Workspace with calendar synchronisation.
Spice AI
Agents within your permissions, with the AI provider of your choice.
Open Core
Source code open to view, your own extensions in separate layers.
Questions about security
No. Open code can be checked by many people. We check it ourselves on every release, with code analysis and scans of dependencies, secrets and containers. Passwords or keys are never in the code, and we fix findings within fixed deadlines. Please report vulnerabilities to office@spicecrm.com. The Open Core page answers further concerns.
Yes. Permission profiles, the audit trail and workflows provide the evidence an ISMS needs. SpiceQMS includes chapter templates for ISO/IEC 27001. We develop Spice itself under an ISMS aligned with ISO/IEC 27001.
Yes. Privacy by design is a fixed part of our development process. Spice stores your customers’ preferences and consents, for example on data processing and marketing approval. You decide where the data lives and who sees it, and every change is on record.
No. Spice AI agents work strictly within your permissions. You choose the AI provider yourselves and connect it through open interfaces.
The same licence price as in the Spice cloud, plus one-off setup. The licence prices are published on the pricing page.
That depends on industry, size and activity. Your industry page names the most important legal sources.
You choose: the Spice cloud in European regions, a dedicated instance or your own data centre. Your permission profiles determine who sees what. The audit trail shows who has accessed which data.
Talk to us.
What are you planning, and what is missing today? We reply personally and tell you plainly whether Spice is the right fit.
- You tell us what you have in mind.
- We get back to you personally by email.
- If you like, we show you Spice in a demonstration.
Prefer to talk directly? office@spicecrm.com+43 (1) 89083610