Do we need to write code to add a new signal?
No. Signals are configuration, created in the console or through the API. Only the first integration, sending events and asking for answers, needs development work.
How fast is it?
Recording an event and answering a question each typically take a few milliseconds or less. Every profile has a time budget, 20 ms by default.
What happens if part of the system is slow or down?
The engine answers with what it could compute in time and lists what is missing. For strict use cases, a profile can refuse to answer instead (fail closed).
Can we test a rule before it affects customers?
Yes. Dry-run it on recent real events, backfill it with history, or run it in shadow next to the current version, then activate it and roll back if needed.
Does it store personal data?
Identifiers are hashed before storage, with a key per tenant, and event data is encrypted inside the system. We advise against storing personal data such as names as entity attributes.
Does it work with our identity provider?
Yes. Services authenticate with OAuth 2.0 / OpenID Connect tokens from Keycloak, Auth0, Microsoft Entra ID, Zitadel, Better Auth and other standards-based providers, or with scoped API keys.
Who can sign in to the console?
Everyone signs in with an Aggrelis account. The person who subscribes becomes the first owner of the workspace and invites the team; each member works with the role an owner gave them.
What happens if a payment fails?
Your workspace keeps running while we retry the payment. If it stays unpaid for 7 days, the workspace is suspended until the payment goes through, then it resumes.
What happens when we cancel?
The workspace runs until the end of the paid period and is then deleted. We can restore it for 30 days. Subscribing again creates a new workspace.
Can we run it in our own infrastructure?
Yes. The engine runs on Kubernetes (Helm chart), Docker or Docker Swarm, with PostgreSQL and Redis, under a signed license file. Contact us for an on-prem license.