Rose Deployment FAQ
Welcome to Rose!
How Do I Get Started with Rose Deployment?
Your journey starts with a kick-off meeting with our onboarding team to begin a Pilot. Together we'll align on the best implementation strategy for your situation, walk you through what to expect, and share all the documents you'll need to get started.
Pilot Deployment
A structured three-step process to get you up and running.
| Step | Description | Implementation Time |
|---|---|---|
| Step 01 — Kickoff Meeting | Kickoff meeting to align on what to expect with this pilot, how we're going to configure your agent, and how data should be transferred. | 1h–2h |
| Step 02 — Technical Integration | Integration, data ingestion, and agent setup aligned with your SOP in line with pilot scope. | 2–4 weeks |
| Step 03 — Agent Fine-Tuning | Once we receive annotated alerts & data, we'll work together to fine-tune the agent to your specific processes. We will illustrate the feedback mechanisms. | 2–4 weeks |
API Integration vs. Case Management Integration
What integration strategy is best for me?
| Approach | How It Works | Pros | Cons |
|---|---|---|---|
| Direct API Integration (Recommended) | Your system pushes alerts, entities, and transactions to our REST API, and we deliver results back via webhooks. | Real-time delivery, full control over timing and payloads, scales cleanly. | Requires engineering resources to build and maintain. |
| Case Management Integration (e.g. Unit21) | We connect to your existing system, check for new alerts on a schedule, and kick off investigations on a batch basis. | No engineering effort on your side. | Batch-based rather than real-time, limited by the source system's API, more expensive to integrate. |
Recommendation: Use direct API integration for production deployments where you have engineering support. Choose case management integration when you don't have engineering resources or want us to handle the connection for you.
How Do I Get Started with Rose API?
We recommend using our Rose API to get started with using Rose. The best place to begin is our Getting started with Rose API documentation. For production use cases, we also recommend using webhooks.
Why Webhooks?
We recommend push-based architecture (webhooks/events) over pull-based (polling) because they provide real-time notifications the moment your data is ready, eliminating the need to constantly poll our API which can miss timing windows.
See webhooks documentation →
What Data Does Rose Need?
We've documented the full data model here: Rose Data Model . Columns marked 'Required: Yes' indicate the minimum data we need to get started. If you have additional data points we don't currently support, let us know and we'll find a way to make it work. We are constantly evolving our schema base on customer need!
See Rose Data model →
We have no engineering resources. Can we still partner?
Absolutely. We have an option for teams that don't have any engineering resources. We do all the heavy lifting: we connect to your existing case management system, automatically check for new alerts each day, perform ETL, kick off Rose investigations, and send the results back to your case management system. All on a daily basis. You can also just send us CSVs and we'll handle the processing on our side.
Do you have an Integration with Unit21?
Yes. We've already done this successfully with multiple clients, and it's running in production today.
We support Unit21 CSV export as well as a direct integration with Unit21, where we pull alerts on a recurring basis and can return the investigation results in Unit21 for your convenience.
Here's how to export CSV files from Unit21. Below are the relevant Unit21 API docs, though the same functionality should be available through their web app UI:
- Export alerts for a given time range and/or set of entities. Be sure to generate the detailed version of the alert, not just the summary: https://docs.unit21.ai/reference/export_alerts
- Export transactions for a given time range and/or set of entities: https://docs.unit21.ai/reference/export_transactions
This will produce three types of CSV files: alerts, entities, and transactions. Please export previously worked alerts — ones that include disposition status and notes — so that Rose can learn from them.
How Does Axle Connect with Different Case Management Systems?
We connect through a custom payload mapping to our REST API. We build a small translation layer that converts your system's alerts, entities, and transactions into the format Axle expects. The scope is well-defined and limited to just those three things, so it's straightforward field-matching rather than a heavy integration project. You can see our data model here .
How is the structured audit trail delivered back to my Case Management System? Is it a consolidated PDF or parsed into independent metadata fields?
Both formats are available, from the same underlying structured data.
I am concerned with security, are your digital workers private, single-tenant instances?
Yes, private, single-tenant instances exclusively — no public LLM APIs.
What are the data retention policies?
The retention period is 90 days after contract termination.