Platform > Security, Governance + Hosting Layer > Deployment + Architecture
Deployment + architecture.
Deploy Rayven where your data needs to live - SaaS, private cloud, on-premise or Edge - with identical platform functionality across all models and no vendor lock-in.
CAPABILITY OVERVIEW
Deploy where your requirements demand.
Rayven supports different deployment models - each delivering identical platform functionality, the same security architecture + the same managed service.
Choose the model that fits your data residency, latency, compliance + infrastructure requirements. Move between models as those requirements evolve. No rebuilding of platform configuration, workflows or application logic is required to migrate between deployment models.
Rayven's team manages the platform in all cases - you retain control of the infrastructure in private cloud, on-premise + edge deployments.
Deployment models available:
-
SaaS via Rayven's managed cloud (Azure, default + zero setup)
-
Private cloud - your own Azure, AWS or GCP tenant
-
On-premise - hardware within your own data centre
-
Edge - local processing close to devices and data sources
-
Hybrid - combinations of the above for specific requirements
KEY CAPABILITIES
What Deployment + Architecture gives you.
SaaS - Rayven's managed Azure cloud
Deploy immediately on Rayven's own Azure infrastructure with zero setup overhead. Rayven manages everything - uptime, backups, patching + scaling. The fastest path to a production deployment with enterprise-grade infrastructure from day one.
Private cloud deployment
Deploy the full Rayven platform stack within your own Azure, AWS or Google Cloud tenant. Identical functionality to SaaS. Your data stays in your cloud environment. Your existing cloud agreements apply. Rayven manages the platform remotely; you retain control of the infrastructure.
On-premise deployment
Deploy Rayven on hardware within your own data centre for maximum data sovereignty + control. Suited to organisations with strict regulatory requirements or security policies that preclude cloud-hosted operational data. Rayven's team manages the platform remotely.
Edge deployment
Deploy Rayven closer to data sources for low-latency, local processing. Suited to industrial environments where real-time decisions must happen at the edge - reducing round-trip latency for time-critical control + automation workflows where cloud connectivity is constrained.
Dev, staging + production environments
Full environment separation with CI/CD pipelines, versioning + controlled environment promotion. Changes are tested in dev and staging before promotion to production. Configuration changes, workflow deployments + application updates go through a managed release process.
Portability - no rebuild required
Migrating between deployment models does not require rebuilding platform configuration, workflows or application logic. Rayven's architecture is designed for portability, protecting your investment in platform configuration regardless of where the platform runs.
HOW IT CONNECTS: EXPLAINER
Where Deployment + Architecture fit in the Rayven Platform stack.
Deployment + Architecture defines the infrastructure model beneath the entire platform.
-
The Integration Layer's connectors, IoT protocols + API endpoints operate within the deployed infrastructure - whether cloud, private cloud, on-premise or Edge.
-
The Data Layer's MySQL + Cassandra databases run on the deployed infrastructure, with data residency determined by the deployment model.
-
The Execution + Presentation Layers run all workflow logic + user interfaces on the deployed compute.
All deployment models deliver identical platform functionality - the same nodes, capabilities + integrations work identically regardless of where the platform runs.
USE CASES
How Deployment + Architecture gets used.
Enterprise deploying within its own Azure tenant for data sovereignty
A financial services firm requires all operational data to remain within their own Azure tenant for regulatory compliance. Rayven deploys the full platform stack within the client's tenant. Rayven's team manages the platform; the client retains control of the infrastructure. Identical functionality to SaaS - without data leaving the client's environment.
Industrial operator deploying Edge nodes for real-time on-site control
A mining operator requires sub-millisecond response times for control automation on-site. Edge deployment nodes run Rayven's workflow execution engine locally, close to connected assets. Real-time control decisions happen on-site; processed data syncs to a central cloud instance for reporting + AI model updates.
Partner deploying isolated private cloud instances for high-security clients
An MSP serving defence + government clients deploys dedicated private cloud instances per client - no shared infrastructure. Each deployment runs in its own isolated environment with its own data residency, security controls + compliance configuration.
Rayven Deployment + Architecture FAQs:
What deployment options does Rayven support?
Rayven supports three deployment models - fully managed cloud (SaaS), hybrid edge-cloud where processing happens close to the source, and on-premises for organisations with strict data sovereignty requirements. See the Security Layer.
Can Rayven be deployed on-premises?
Yes. Rayven can be deployed within a customer's own data centre or private cloud environment. This is common for regulated industries, defence-related organisations, and deployments with strict network isolation requirements. See Hosting + Management.
What cloud providers does Rayven support for hosted deployments?
Rayven's managed cloud deployments run on AWS and Azure. The choice of provider can be matched to existing infrastructure, data residency requirements, or enterprise cloud agreements. See Hosting + Management.
What is the Rayven Edge deployment model?
Rayven Edge places lightweight processing nodes physically close to data sources - such as factory floors or remote sites - reducing latency and enabling local operation if connectivity is disrupted. Data is synchronised to the central platform when available. See IoT Devices + Protocols.
How does Rayven handle high availability and redundancy?
Managed cloud deployments use load balancing, redundant database replication, and automated failover. Architecture is designed for high availability with defined recovery time objectives for critical components. See Hosting + Management.
Can multiple Rayven environments be maintained?
Yes. Separate development, staging, and production environments can be provisioned, allowing changes to be tested before promotion to the live environment. Configuration can be migrated between environments in a controlled manner. See Governance + Controls.
What databases does the Rayven platform use?
Rayven uses MySQL for structured relational data and Apache Cassandra for high-velocity time-series data. This dual-database architecture is optimised for both transactional and time-series operational workloads. See SQL + Cassandra Storage.
Does Rayven support containerised deployment?
Yes. Rayven's platform components are containerised using Docker and can be orchestrated with Kubernetes for scalable, consistent deployments across cloud and on-premises environments. See Hosting + Management.
What are the network requirements for a Rayven deployment?
Cloud deployments require outbound HTTPS access to Rayven's endpoints. Edge deployments need reliable connectivity to the central instance and inbound access from data source protocols such as MQTT, Modbus, or OPC-UA. See IoT Devices + Protocols.
Can the deployment architecture be customised for enterprise requirements?
Yes. Rayven's deployment architecture is configurable. Compute sizing, database storage tiers, network topology, and backup schedules can all be tailored to match enterprise performance and compliance requirements. See Hosting + Management.
Also in Security, Governance + Hosting:
White Labelling
Custom domain, branding, colour palette + multi-tenant configuration for client-facing applications.
Hosting + Management
Managed cloud hosting on AWS + Azure, SLA-backed uptime, automated backups + disaster recovery across all deployment types.
Users, Roles + Access
Role-based access control, SSO, MFA + workspace-level permission management across all users.
Usage + Metrics
Real-time visibility of platform usage, workflow performance, data volumes + resource consumption.
Enterprise Security
Encryption at rest + in transit, network segmentation, secrets management + compliance-ready governance.
Governance + Controls
Data retention policies, deployment controls, rate limits + environment isolation across the platform.
Audit Trails + Logs
Complete, immutable records of every user action, data change + workflow execution across the platform.
Want to discuss your hosting requirements?
Tell us where your data needs to live and we will walk you through the right deployment option for your environment.
Join the Shift
Discover the easy way to do something new.
Book a free 30 minute assessment with our team and we'll scope your project, needs + what a solution might look like.