Parachute vs Resolve Onboarding and Offboarding Automation

Parachute automates security incident response through web and API access. It can run a configured response when an alert matches, with runbooks authored in YAML or a visual editor, version controlled in Git, and tested with simulated alerts. The service can isolate hosts through AWS, GCP, and Azure APIs, and gather logs, process lists, network flow captures, and memory snapshots into packaged, hashed evidence. Listed integrations include PagerDuty, Opsgenie, Datadog, Splunk, AWS, GCP, Azure, Slack, Microsoft Teams, Jira, Linear, and Elastic/Kibana. Webhook-capable tools can trigger a runbook, and the REST API accepts custom alerts. The maker says data in transit uses TLS 1.3 and stored data uses AES-256-GCM; inbound webhooks are checked with HMAC-SHA256 and a five-minute timestamp tolerance. It says incident data is not used to train AI models and evidence is deleted after its configured retention period. Founded in 2024 and based in Sydney, Parachute offers a free Developer plan, a 14-day trial, and paid plans from $49/mo. SOC 2 Type II is planned but not yet certified; ISO 27001 is on the roadmap.

Resolve Onboarding and Offboarding Automation coordinates employee lifecycle changes across HR, identity, and IT systems. Onboarding workflows can create accounts, assign entitlements, provision email, VPN, and SaaS applications, deliver software, and notify managers and new hires. Offboarding can disable accounts, revoke tokens, reclaim licenses, trigger device wipes or locks, archive mailboxes, and record actions. HRIS or identity-provider events can start workflows, with actions based on role, location, and department; manual submissions through RITA are also available. The workflow checks licensing, inventory, and access states, flags exceptions with diagnostics, and updates CMDB, ITSM, HRIS, and audit systems. Resolve names AD, Azure AD, and Okta for account creation. Its open integration framework connects custom or legacy tools through REST APIs, SNMP, SSH, TCP, SMTP, or SOAP. The paid product runs through API, self-hosted, and web deployments; pricing is on request.