Support
FAQ
Frequently asked questions about Ryvn
Platform Overview
What is Ryvn and how is it different?
What is Ryvn and how is it different?
Ryvn is a deployment platform that puts you in control of where your applications run. We’ve reimagined cloud deployment to work the way enterprise software should - your apps run directly in your cloud accounts or your customers’ environments. This is game-changing for enterprise SaaS companies who need to meet strict data residency and security requirements.Our platform gives you a streamlined deployment experience across any cloud provider. Push updates to AWS, Azure, or Google Cloud with the same consistent workflow. You keep full deployment control while your customers maintain sovereignty over their infrastructure and data. Learn more about how Ryvn works and why BYOC is transforming enterprise software delivery.
How does Bring Your Own Cloud (BYOC) work?
How does Bring Your Own Cloud (BYOC) work?
BYOC is our core deployment model. Most PaaS platforms host your applications in their own cloud infrastructure, but Ryvn takes a different approach. We deploy directly to your customers’ cloud accounts - whether AWS, Google Cloud, or Azure. You maintain full deployment control through our platform while your customers keep their applications and data in their own cloud environment.The provisioning process is straightforward: your customer provides limited cloud credentials, and Ryvn automatically sets up the necessary infrastructure in their environment - from VPCs to Kubernetes clusters. Once provisioned, you can deploy and manage applications just like you would in your own cloud, while your customers maintain complete control over their infrastructure and data.
What problems does Ryvn solve?
What problems does Ryvn solve?
We tackle the biggest headaches in enterprise software delivery. Traditional on-premises deployments bog teams down with infrastructure work - managing Kubernetes, Terraform, containers, and more. Meanwhile, traditional SaaS models often can’t meet enterprise security requirements. We solve both problems: deploy straight to customer clouds while automating all the infrastructure complexity.This means no more wrestling with Kubernetes configs or waiting weeks for customer DevOps teams. Start enterprise POCs in days instead of months, with your app running right in their environment. Plus, you get direct access to their internal services without complex networking hoops. It’s like having a DevOps team that never sleeps, handling all the infrastructure complexity while you focus on your product. Ready to see for yourself? Check out our quickstart guide.
What types of applications can I deploy?
What types of applications can I deploy?
Whatever you’re building, we’ve got you covered. Need to run a web app? Our Server type handles everything from SSL to auto-scaling. Got background tasks? Workers process your async jobs reliably. Running scheduled backups? Jobs execute right on time. For the Kubernetes pros, deploy custom Helm charts. And yes, you can manage infrastructure too with our Terraform support. Each type is optimized for its use case, so you get the right features without the complexity. See our service type comparison for detailed feature breakdowns.
Getting Started
How do I deploy my first application?
How do I deploy my first application?
Getting started takes just a few steps. Head to control.ryvn.app, connect your code source (GitHub repo, container registry, or Dockerfile), and choose your target cloud. Pick your service type (Server for web apps, Worker for background tasks, or Job for scheduled work), configure your environment variables, and we handle the rest. We’ll provision the infrastructure, set up your deployment pipeline, and give you a unique ryvn.app URL. Want the details? Check out our deployment guide.
What deployment sources are supported?
What deployment sources are supported?
Use whatever works best for your workflow. Push straight from GitHub for tight
integration with your development process. Already have containers? Deploy directly from any
registry. Need custom builds? We’ll handle your
Dockerfile. Running complex apps? Use Helm
charts. Moving existing workloads? We’ll help migrate them. The source doesn’t
matter - we’ll get your app running reliably.
How does environment setup work?
How does environment setup work?
We’ve made environment setup secure and painless. Generate an installation link for your customer, they create temporary credentials with limited scope (or follow manual steps if they prefer), and we handle the rest. Our provisioning system sets up all the necessary infrastructure - VPCs, Kubernetes clusters, load balancers, the works. Once done, you’re ready to deploy. No more waiting for customer DevOps teams or managing complex infrastructure yourself. Check out our cloud-specific guides for AWS, Google Cloud, and Azure provisioning.
Deployment & Operations
How do zero-downtime deployments work?
How do zero-downtime deployments work?
Our zero-downtime deployment process is smooth and safe. We create new instances with your updated code, verify they’re healthy, and gradually shift traffic over. The old version keeps running until the new one is proven ready. If anything goes wrong? The deployment automatically cancels, traffic stays on the working version, and you get instant notification. Your users never see an error page - just continuous uptime. Check out our guide on maximizing uptime for best practices.
How does release management work?
How does release management work?
Take control of your release process. Use release channels like ‘pre-production’ and
‘stable’ to stage deployments across environments. Need to roll back? One click restores your
previous state. Want approval gates? Add them to critical environments. Track every deployment and configuration
change in your audit history. Schedule updates during maintenance windows. It’s like having guardrails for your
deployment process.
How are maintenance and updates handled?
How are maintenance and updates handled?
You control how updates roll out to your customer environments through maintenance windows. Each customer can configure their own maintenance window - specifying when they’re comfortable receiving updates to their environment. This is particularly important for enterprise customers who need to coordinate updates with their own release schedules.When you push an update, Ryvn respects these maintenance windows, automatically scheduling the deployment to occur during the customer’s specified time. Everything happens with zero downtime, and if anything looks off, our automated rollback system kicks in to ensure stability.
How does auto-scaling work?
How does auto-scaling work?
Your services scale intelligently based on real-world demand. We monitor CPU utilization (targeting 70-80%) and memory usage (targeting 80-85%), maintaining at least two replicas for high availability. Each service type has optimized scaling behaviors - web services scale on request load, workers on queue depth, and jobs on execution time. Track scaling events and resource usage in real-time through our dashboard. Want to fine-tune? Adjust thresholds and limits in your scaling configuration.
Monitoring & Troubleshooting
What monitoring capabilities are included?
What monitoring capabilities are included?
Get comprehensive visibility into your services. Track system metrics (CPU, memory, disk) for individual replicas or service-wide aggregates, with 30-day retention. Monitor network traffic with request rates and status codes. Our lightweight monitoring agent (< 1% CPU, < 100MB memory) collects everything automatically. Need the data in your tools? We integrate with your existing observability stack or can store metrics in your cloud. Set up alerts for proactive monitoring and check deployment logs for troubleshooting.
How are health checks configured?
How are health checks configured?
Health checks keep your services reliable. We verify each instance before sending traffic,
automatically detect and isolate unhealthy ones, and restart them if they don’t recover. If new deployments fail
health checks, we cancel the rollout before it affects users. It’s like having an automated operations team watching
your services 24/7.
What should I do if something goes wrong?
What should I do if something goes wrong?
We make troubleshooting straightforward. Start with deployment logs to see what changed. Check health status and resource metrics to spot bottlenecks. Review application logs for errors. Need to go back? Use one-click rollback. Still stuck? Enterprise customers get instant access to our senior engineers. We’re here to help you resolve issues fast and prevent them from happening again. Get familiar with Kubernetes basics and the Ryvn agent for deeper debugging capabilities.
Best Practices
What are deployment best practices?
What are deployment best practices?
Set yourself up for success with our deployment best practices. Use semantic versioning to track releases clearly. Set appropriate resource limits to prevent noisy neighbors. Implement health checks for reliable deployments. Stage changes through pre-production environments. Enable automatic rollbacks as a safety net. Monitor key metrics to spot trends. Think of it as your deployment checklist for production readiness. Learn more about service configuration options.
What are the application requirements?
What are the application requirements?
Make your apps cloud-ready. Whether you’re deploying from GitHub, a
Dockerfile, or a container registry, you’ll need
to define clear entry points and listen on the specified port. Handle shutdown signals gracefully for clean container
restarts. Specify dependencies explicitly to ensure consistent builds. Use semantic versions for predictable updates.
Add health endpoints for reliable deployment checks. Following these cloud-native practices ensures smooth operations
in any environment.
How should I organize environments?
How should I organize environments?
Build a promotion pipeline that works. Use development for rapid testing, staging for pre-release validation, and production for your live service. Create isolated environments for each customer. Control updates using release channels - promote changes from development through staging before hitting production. It’s a proven structure that scales from startups to enterprises. Learn more about environment management and installation best practices.
Support
What support options are available?
What support options are available?
Enterprise customers get the white-glove treatment. Our senior engineers are available 24/7 with 15-minute response
times for critical issues. You’ll have a dedicated technical account manager who knows your setup inside and out.
Need help? Jump into your private Slack channel for instant support. We’ll even help migrate your existing
infrastructure and back it all with a 99.99% uptime SLA. Think of us as an extension of your DevOps team. Visit our
support page to learn more.