Filigran Deployment & Onboarding Services
How Filigran deploys the platform and onboards your team - from kickoff to business-as-usual.
Platform Deployment
For SaaS and Bring Your Own Cloud (BYOC) customers, the Filigran team will manage the deployment of the platform and requested standard connectors to integrate the solution. Customers must provide the Filigran team the required access and resources such as API keys, open network flows, or other necessary configuration details. Filigran provides guidance, documentation, and support to ensure that the deployment proceeds smoothly under these conditions.
For On-Premises customers, Filigran will provide documented deployment options for the on-premises platform, e.g. assisted deployment via Helm charts, as well as technical support. The actual execution of the platform deployment is the responsibility of the customer. Architecture workshops and documentation for air-gapped deployments can be scoped and contracted as Professional Services with a Statement of Work.
Onboarding
Filigran Onboarding is designed to make the Customer autonomous in the day-to-day use of the platform for their identified use cases. Filigran does not perform hands-on implementation of use cases on behalf of the Customer — execution and operationalization are the Customer’s responsibility. The Onboarding program is delivered through remote live sessions with the Customer Success team, focused on standard platform usage and configuration.
Advanced Training: standard Onboarding does NOT attempt to provide advanced product expertise (eg: deep-dive scenarios into advanced use cases). To develop advanced skills, Customers can separately purchase advanced-level Filigran Academy subscriptions or Instructor-Led Training courses. Custom Instructor-Led courses or events can be scoped and contracted with a Statement of Work.
The Onboarding program follows four phases:
Phase 1: Kickoff & Scope Alignment (Kickoff – Week 1)
- Kickoff meeting: introduction of the Filigran Customer Success team, alignment on business objectives, success criteria, and key stakeholders
- Scope confirmation: validation of the use cases to be implemented and integration targets
- Onboarding plan: shared timeline with milestones, RACI, and cadence of touchpoints
Phase 2: Platform Orientation & Configuration Guidance (Estimated Weeks 2-3)
- Platform walkthrough session(s): guided tour of core capabilities (data model, knowledge graph, dashboards, administration)
- Configuration best practices: taxonomy customization, confidence levels, data deduplication, user roles & access control
- Connector enablement: guidance on deploying and configuring available open-source connectors for data ingestion and export
Phase 3: Use Case Enablement (Estimated Weeks 3-6)
- Use case workshops: remote sessions focused on the Customer’s identified use cases (threat intelligence ingestion & enrichment, indicator lifecycle management, dashboards & reporting, playbook automation, case management & investigations)
- Best practices documentation: access to Filigran’s knowledge base, standard operating procedures, and use case templates
Phase 4: Go-Live & Transition to BAU (Estimated Weeks 5-8)
- Go-live checkpoint: review of platform readiness, connector health, and initial use case operationalization
- Autonomy validation: confirmation that the Customer can independently perform core operations on their identified use cases
- Transition to Business-as-Usual: handover to ongoing Customer Success cadence (regular check-ins, health reviews, and access to technical support per the contracted support level)
Customer Responsibilities
- Designate a project lead and key stakeholders for the onboarding
- Provide required access and resources (API keys, network flows, credentials) in a timely manner
- Attend scheduled sessions and complete assigned actions between workshops
- Execute the implementation and operationalization of use cases on the platform
Integrations / Connectors
Filigran provides a broad catalog of integrations and connectors which are available to Customers in their current state. All integrations are open-source and publicly accessible, allowing full visibility into their capabilities, compatibility, and configuration requirements. Customers may freely deploy and use any of these integrations as part of the platform’s included functionality.
Any additional integration needs, such as the development of new connectors, modifications to existing connectors, or introduction of enhanced non-standard behavior must be scoped and contracted in a Statement of Work.