Casewhere
Casewhere is an integration-first platform for case management, process standardization, and workflow automation. It ties together the applications, people, and data your organization already depends on — and automates the work that moves between them.
What is Casewhere?
Casewhere makes it possible to create seamlessly integrated processes that connect applications, internal and external actors, and data stores into one coordinated flow.
What sets Casewhere apart from other case management and workflow tools is its philosophy: it does its best not to become yet another database inside your company. Wherever possible, Casewhere integrates with the systems you already run rather than replacing them. Thanks to an extremely open architecture, it can read and write data in real time — from Active Directory, databases, email servers, and web services — instead of forcing you to duplicate and synchronize that data.
Because of this, Casewhere is better described as a platform than as a finished application. It ships without even the most common predefined objects such as Users and Groups, and instead lets you build an almost endless number of specialized solutions on top of it.
The problem: great systems, working in silos
Most organizations already run excellent systems — finance, HR, CRM, logistics, online sales. The problem is that these systems operate in functional silos. They may share data, but they rarely react to what happens elsewhere, so people are left to move "cases" along by hand.
- Hiring a new employee. The recruitment system won't tell HR to send a contract, raise an IT request for a laptop, set up accounts and access rights, send the welcome letter, notify colleagues, or collect the information needed before day one.
- A customer support issue. The CRM may run the support process, but it won't ramp up production of a broken part, alert the Key Account Manager, set a delivery deadline with shipping, or follow up with the customer afterward.
Casewhere closes these gaps while letting your existing systems keep working exactly as they do today. Its open architecture lets it react to events in one system, push data into another, interact by email and online forms, and make decisions based on the business logic you configure.
flowchart LR
AD[Active Directory] <--> CW
CRM[CRM] <--> CW
ERP[ERP / finance] <--> CW
MAIL[Email / messaging] <--> CW
WS[Web services / APIs] <--> CW
CW{{Casewhere orchestration layer}}
CW --> A1[Automated workflows]
CW --> A2[Self-service portals]
CW --> A3[Audit and compliance]
CW --> A4[REST API and BI]
style CW fill:#1f6feb,color:#ffffff,stroke:#11448a
How Casewhere thinks: processes and cases
Everything in Casewhere starts with a process — a repeatable business procedure you want to support, such as "Apply for a job." Every time that process runs, Casewhere creates a case to manage and track it. The case is the single place that holds the collected data, status, communication history, people involved, deadlines, and progress for that one instance.
A process is governed by workflows, organized into steps and activities. Activities are either forms (to display data or collect input from users) or scripts (to automate work behind the scenes). This structure scales from a single form to complex, branching, multi-step automation.
flowchart TD
P["Process — template (Apply for a job)"] -->|each run creates| C["Case — one application"]
C --> D1[Documents and data]
C --> D2[Messages and history]
C --> D3[Status and deadlines]
C --> D4[People involved]
P -->|governed by| W["Workflows — steps and activities"]
W --> F[Form activities]
W --> S[Script activities]
Because Casewhere doesn't impose a data model, you decide what a case contains. You could use it for inventory, manufacturing, sales, services, help desk, or finance — but its real strength is tying specialized systems together and making sure the dependencies between them are automated, administered, and audited.
What you can build
| Capability | What it means for your business |
|---|---|
| Flexible data modeling | No fixed schema — model any entity (Employee, Application, Invoice) with relationships, validation, encryption, and search built in |
| Workflow automation | UI and fully automatic workflows triggered by users, schedules, data changes, system events, or external systems |
| Rule-based logic | Encode business decisions as C# rules — access control, navigation, validation, triggers, and GDPR anonymization |
| Worker sites | Multiple branded, independently secured front-ends — public portals, staff back-office, configuration sites — from one solution |
| Integration and data sources | Pull from and push to external systems with REST and scripted data sources |
| Extensibility | Go beyond configuration with themes, a CMS, and a .NET plugin framework |
Enterprise-grade by design
Casewhere is built for regulated, security-conscious organizations. Compliance and control are part of the platform, not bolt-on extras.
| Area | Capabilities |
|---|---|
| Access control | Layered, deny-by-default permissions at site, page, widget, action, data source, data class, and field level |
| Data protection | Field-level encryption for sensitive data (PII, SSNs), HTTPS everywhere, and optional encryption at rest |
| GDPR | Built-in right-to-be-forgotten with data masking, pseudonymization, and generalization rules |
| Audit trail | Event-sourced, immutable logging of read and write access — exportable to your SIEM or analytics platform |
| Authentication | SAML 2.0 identity providers — Azure AD, NemLogin (MitID), Safewhere Identify — with claims-based access control |
Casewhere's OWASP Top 10 defense-in-depth approach combines zero-trust validation, parameterized queries, and immutable event sourcing, so every data change is traceable and every access attempt is logged.
Built to integrate
Open architecture is the whole point. Casewhere exposes and consumes data through well-defined, secured mechanisms.
| Mechanism | Use it for |
|---|---|
| REST data source | Securely expose data (read / write / delete) to partners and BI tools such as Power BI, protected by API keys |
| Web trigger | Let an external system start or continue a workflow through a Web API endpoint |
| Webhooks | Push notifications to subscribers the moment data changes |
| Plugins | Service-side and client-side .NET integrations — CVR lookup, PDF generation, SFTP, SMTP, and more |
| Scripting data source | Advanced reporting with MongoDB aggregation pipelines |
Because workflows can run fully unattended, an external system can start a process, let Casewhere maintain the state, logging, and business rules, then check back later for the result — moving the UI elsewhere while Casewhere orchestrates the work.
From model to production
A typical Casewhere solution comes together in five steps:
flowchart LR
M["1 · Model data<br/>(data classes)"] --> PR["2 · Define processes"]
PR --> WF["3 · Build workflows<br/>(forms and scripts)"]
WF --> R["4 · Configure rules<br/>(access, navigation, triggers)"]
R --> UI["5 · Design the UI<br/>(pages, widgets, worker sites)"]
When it's time to ship, Casewhere DevOps bundles an entire solution into a single deployment package that an IT operations team can promote across environments through Casewhere Admin — no deep knowledge of the contents required.
flowchart LR
DEV -->|Internal test| QA
QA -->|User acceptance test| PRE-PROD
PRE-PROD -->|Go-live| PROD
To get to market even faster, start from ready-made products — installable applications, components, integrations, plugins, and themes you can drop into your solution.
Why choose Casewhere?
Compared with more closed case management and workflow tools, Casewhere's open, integrate-don't-replace approach delivers:
- Quick implementation — build on the systems and data you already have
- Low organizational resistance — existing systems keep working unchanged
- Lower cost — less duplication and less custom integration code
- Easier maintenance — far less data synchronization to manage
- Compliance you can prove — security, audit, and GDPR tooling built in
Start building
| Go to | For |
|---|---|
| Get started — Try it! | A hands-on tutorial that builds a real application step by step |
| Fundamentals | The core building blocks: data, processes, workflows, rules, and UI |
| Products | Ready-to-install applications, components, plugins, and themes |
| Releases | Release notes and upgrade guidance |
Casewhere is not always easy to explain, because its power lies in filling the gaps between other systems rather than owning a single domain. The fastest way to understand it is to build something — so let's get started!