How It Works
Chrysalis Cloud is designed for services that require persistent connection on the edge, such as video cameras, and for the execution of resource intensive AI-based jobs.
Chrysalis Cloud Architecture
The Chrysalis Cloud Orchestrator is designed to utilize nearly 100% of available resources for highly demanding computational jobs.
Chrysalis Cloud SDK
Python SDK with access to stream/pull video frames
Chrysalis Edge Proxy
Collects and mitigates firewall restrictions within organizations and for end-to-end secure streaming
Chrysalis Monitor
Monitors streaming containers (and ML nodes). Fires alarms based on Chrysalis Video Tags.
Chrysalis Video Storage
S3 compatible video storage
Chrysalis Video Tags
Collection of video tags (query enabled and relatable to Video Storage)
HOW CHRYSALIS CLOUD COMPARES
 Kuberenetes |  AWS Lambda |  AWS Fargate |  Chrysalis Cloud | |
|---|---|---|---|---|
AUTOSCALING | Customizations
are complex | Built-in but no job
packing | Built-in | Built-in, easy |
SUITABLE FOR VIDEO
INGESTION
(Edge IoT) |  | | Need customized
solutions (running
on separate
service like EKS) |  |
SUITABLE FOR
RESOURCE
INTENSIVE JOBS | (*Requires complex customizations) | | | |
CLOUD AGNOSTIC | (*Requires re-configuration) | (*only AWS) | (*only AWS) | Built-in, seamless |
EASE OF USE | Intricate UI
| Simple UI only | Simple UI only | Simple API & SDK |
QUALITY OF SERVICE | | | | |
MINIMUM REQUIRED
HUMAN RESOURCES
(for 24/7 operation) | 3 | 0 | 1 | 0 |