Where ValueSpoc runs and what it connects to
The platform connects to your existing systems and runs in Germany, in Enterprise also in your own data centre.
You choose where your data lives
- IONOS
- Kubernetes
- Helm
- Keycloak
ValueSpoc runs with IONOS in Germany or, in Enterprise, with Helm on your own infrastructure. Sign-in can go through your identity service via OIDC.
Work and ticket systems
- Jira
- ServiceNow
- Microsoft Dataverse
Work packages go into the system where delivery happens, and status comes back on schedule. Each connection is enabled per organisation.
Notifications and dates
- Microsoft Teams
- Microsoft Outlook
- Google Calendar
Notifications from the steering data reach your team in Teams or by e-mail. Status meetings, reporting deadlines and board sessions appear in the calendar of the people involved.
Collaboration and documents
- Confluence
- Google Drive
Files from Google Drive go into the document room. Confluence pages turn into suggestions for projects, risks and status reports, which a person approves.
Language models
- IONOS AI Model Hub
- Mistral
- OpenAI
- Anthropic
- Google Gemini
The default is the IONOS AI Model Hub in Germany. From Professional your organisation adds the other providers on this list itself, with its own access key.
Open interfaces
- REST
- OpenAPI
- Webhooks
The core objects are reachable and exportable through a documented REST interface with OpenAPI. Events go out as a signed feed to adjacent systems.
The target system stays in the lead
ValueSpoc creates work packages in the target system and reads the status back. That keeps it clear where the leading state lives.
Does this fit your system landscape?
Book a callAll trade marks named are the property of their respective owners. Naming them describes technical connectivity and implies no partnership.