DigitalOcean Alternatives That Save Time and Cost in 2026

✨ Summarize this content with AI

CHATGPT PERPLEXITY GROK GOOGLE AI

If you are searching for the best DigitalOcean alternatives in 2026, you are probably trying to solve a practical problem: how to deploy and run your application without spending hours managing infrastructure and pipelines.

The way developers build and ship software is changing faster than the infrastructure beneath it. The Stack Overflow 2025 Developer Survey found that 80% of developers now use AI tools in their workflows, and that shift is rapidly reaching infrastructure, too. 

DevOps automation emerged as a new mainstream use case in 2025, with 38% of engineering teams now applying AI directly to deployment and operations workflows, up from near zero just two years prior.

Developers today are no longer just comparing infrastructure providers. They are comparing how much operational work a platform removes. Managing CI/CD pipelines, configuring deployments, setting up monitoring, handling scaling rules, and controlling cloud costs can quickly become a full-time responsibility.

AI-driven platforms are now starting to change this workflow. Instead of asking developers to define how deployments should work, modern platforms use agentic AI to automate the entire process, detecting the application stack, configuring the build pipeline, deploying services, scaling infrastructure, and monitoring performance automatically.

That shift is why many developers and startups are moving away from traditional infrastructure platforms and looking for alternatives that remove DevOps complexity rather than adding more tools.

This guide compares the best DigitalOcean alternatives based on automation, pricing, and long term maintainability, including AI native platforms that handle deployment end-to-end.

TL;DR, What You Need to Know

• Most DigitalOcean alternatives still leave the operational work to you. Moving from one VPS or cloud provider to another often shifts the deployment and infrastructure tasks; it does not remove them. Developers still configure CI/CD pipelines, manage infrastructure, and handle scaling as their applications grow.
• AI is beginning to reshape DevOps workflows. According to research from Kratix, 88% of platform engineers now use AI daily, and 90% expect AI to significantly transform how infrastructure and deployments are managed in the coming years.
• This guide compares the best DigitalOcean alternatives in 2026, including platforms like Kuberns, Render, Railway, Fly.io, and Qovery. We break down pricing, strengths, limitations, and ideal use cases to help you choose the right platform.
• If your goal is to stop managing infrastructure and start shipping faster, newer platforms built around automation and agentic AI, such as Kuberns, can handle the entire deployment workflow automatically, detecting your stack, configuring the build pipeline, deploying the project, and managing scaling and monitoring without manual setup.

Comparison of the Best DigitalOcean Alternatives (2026)

Before diving into the full reviews, here’s a quick snapshot of how the top platforms compare.

Platform	Agentic AI Deployment	Deployment Experience	CI/CD	Pricing Model	Best For
Kuberns	Yes, full-stack Agentic AI automation	One-click deployment	Built in, zero setup needed	Pay only for compute, no per-user fees	Teams that want fully automated deployments without DevOps
Render	No	Git based deploy with manual configuration	Built in but requires setup	Per service pricing	Full-stack apps that need a Heroku-style platform
Railway	No	Near-zero config deploy	Limited CI/CD support	Usage-based with limits	MVPs, small projects, and prototypes
Fly.io	No	Docker-based CLI deployment	External CI/CD required	Usage-based infrastructure pricing	Global apps that need edge deployment
Qovery	No	Kubernetes-based deployments	Built in GitOps workflows	Team-based pricing	Teams adopting Kubernetes infrastructure
Vercel	No	One-click deploy for frontend apps	Built in	Per-user pricing on Pro	Frontend apps built with React or Next.js

What this table shows clearly: Kuberns is the only platform here that combines agentic AI deployment, one-click deploy, built-in CI/CD, and no per-user pricing in a single package. Every other platform makes you trade at least one of the features off.

These are the Top DigitalOcean Alternatives in 2026

When evaluating the top alternatives to DigitalOcean in 2026, it’s important to understand what each platform does best, what limitations to expect, and which use cases they’re optimised for. Below is a comparison of seven leading alternatives.

1. Kuberns

Best for: Teams that want an agentic AI-powered deployment platform that removes infrastructure and DevOps work

What Makes Kuberns Different

Most deployment platforms are tools. They give you a better interface for doing the same underlying work, configuring pipelines, setting scaling rules, managing environments, and watching dashboards. The operational thinking still belongs to your team.

Kuberns is built on a different model entirely. Kuberns is an agentic AI-powered cloud platform built for developers who want to deploy and scale applications without managing infrastructure.

As the only agentic AI-powered deployment platform available today, instead of asking developers to define how deployments should work, the platform uses agentic AI to manage the entire deployment workflow automatically. Once you connect your GitHub repository, the AI analyses your codebase, detects the technology stack, prepares the build environment, provisions infrastructure, and deploys the application.

From that point forward, the platform continues to manage scaling, monitoring, and cloud operations automatically. (The entire process, from connecting a repository to a live app, is covered in the Kuberns Getting Started guide.)

The result is a deployment experience where developers focus on writing code while the agentic AI system handles the operational side of running applications.

Key Capabilities of Kuberns Agentic AI

One-click deployment from GitHub: Connect your repository and deploy in minutes. Kuberns handles build detection, environment provisioning, SSL certificates, and custom domain setup automatically on every push no configuration required between deploys. See real examples of this in action: deploying Strapi with one-click AI or self-hosting n8n automation workflows without any server setup.

Smart stack detection across major frameworks: Supports Node.js, Python (Django and Flask), Go, Ruby, Java, and more. No manual runtime selection, no Dockerfile maintenance, no dependency management overhead. Check the full list of supported templates and frameworks.

Infinite CI/CD built in, no external tools needed: CI/CD is not an integration you configure, it’s built into the platform with unlimited minutes and deployments. Every push triggers an automated pipeline: build, test, deploy, verify. Staging environments, rollback recovery, and zero-downtime deploys are included from day one.

Full observability, real-time monitoring and alerts: Logs, performance metrics, uptime monitoring, and alerting are built in. No third-party integrations to wire up, no dashboards to build from scratch.

No per-user fees, no platform tax: You pay for the actual compute your applications consume. No per-seat charges, no platform fees, no tier upgrades to unlock core features. Most teams save up to 40% on infrastructure costs compared to equivalent setups on DigitalOcean or AWS. See exactly how Kuberns pricing works and compare plans with a live calculator.

Production-ready from the first deploy: SSL certificates, staging environments, rollback recovery, and zero-downtime deploys are not add-ons. They’re included automatically. Trusted by 3,000+ builders shipping production apps today.

“For a deeper look at how AI is reshaping the developer workflow beyond just deployment, including coding, testing, and iteration, it’s worth understanding the full shift happening in 2026.”

2. Render

Best for: Full-stack developers seeking a Heroku-style platform with more flexibility and better scaling for production workloads

Overview: Render is a modern Platform as a Service (PaaS) built to simplify app hosting without locking you into infrastructure details. It supports a wide variety of application types, including web services, static sites, APIs, background workers, and cron jobs, making it suitable for both MVPs and production environments. Developers can deploy directly from Git with minimal setup, and the platform handles SSL, autoscaling, domain management, and continuous deploys.

It aims to offer a middle ground between the simplicity of Heroku and the power of self-managed infrastructure, while still keeping the developer experience front and centre.

Key strengths:

• Git-based continuous deployment: Automatic deploys triggered by Git pushes with support for private and public repos
• Autoscaling: Services can scale based on load, making Render suitable for both early-stage projects and growing apps
• Preview environments: Automatically spins up preview deployments for each pull request to streamline testing and reviews
• Support for jobs and databases: Offers native support for background workers, cron jobs, PostgreSQL, Redis, and persistent volumes
• Custom domains and SSL included: All services include HTTPS out of the box with zero configuration

Limitations:

• YAML configuration: Some users find Render’s render.yaml structure less intuitive, especially for multi-service apps or complex environments
• Scaling costs: As usage grows, particularly with bandwidth-heavy apps or high-traffic APIs, costs can increase rapidly and become less predictable.
• Limited control for advanced scenarios: While great for most use cases, Render may not offer the fine-tuned customization required for large enterprise infrastructure.

Render is a solid option for developers who want a smooth Git-driven deployment experience and built-in scaling features, without jumping into raw infrastructure.

For a deeper look at how Render handles production workloads and scaling limits, the full breakdown covers pricing tiers, autoscaling behaviour, and where it fits best.

3. Railway

Best for: Quick MVPs, solo developers, and small-scale applications that need instant deploys without setup

Overview: Railway is a lightweight cloud development platform designed to help developers launch apps with minimal friction. It offers a zero-config experience with automatic detection of your tech stack and seamless GitHub integration. You can deploy web apps, APIs, and services within seconds, making it ideal for testing ideas, building MVPs, or powering personal tools.

Railway abstracts away most of the DevOps work, allowing users to focus on writing code instead of managing infrastructure. While it’s intuitive and fast for beginners, it lacks some of the production-grade capabilities required for scaling applications or supporting complex workflows.

Key strengths:

• Zero-config Git-based deploys: Just connect your GitHub repo, and Railway builds and deploys your project automatically
• Beginner-friendly UI: Clean interface that makes it easy to manage services, view logs, and set environment variables
• Built-in integrations: Offers simple plugins for PostgreSQL, MySQL, Redis, storage, and other services without needing manual setup
• Instant previews: Live previews for every change help speed up development and collaboration
• Free tier available: Great for trying out ideas or hosting small apps at no cost

Limitations:

• Basic monitoring and metrics: Lacks deep observability tools or integrated APMs that larger apps may require
• Limited infrastructure control: Not ideal if you need to fine-tune resource allocation or configure custom networking
• No built-in CI/CD pipelines: While deploys are automatic, complex CI/CD workflows require external tooling
• Pricing concerns for production use: Costs can scale quickly with bandwidth usage or high-performance requirements, making it less cost-effective for growing apps

Railway works best as a quick-start platform for new projects or low-risk environments. For production-grade needs, developers may outgrow its capabilities and look for more powerful options like Kuberns or Render.

For teams evaluating whether it can support production-grade CI/CD and scaling requirements, the detailed breakdown covers where Railway excels and where teams typically hit its limits.

4. Fly.io

Best for: Developers building globally distributed applications, latency-critical services, or apps that benefit from edge computing

Overview: Fly.io is a powerful platform designed to run applications closer to end users by deploying them on a network of edge locations around the world. It’s especially useful for teams building real-time services, multiplayer games, or international applications that demand fast response times and low latency. Fly.io supports Docker-based deployments and gives developers deep control over how and where their apps run.

With Fly.io, apps are automatically distributed across multiple regions, and traffic is intelligently routed to the nearest instance. Developers can also configure persistent storage, define secrets, manage clusters, and scale horizontally. While the platform offers flexibility and performance, it does come with a steeper learning curve compared to other PaaS solutions.

Key strengths:

• Global edge hosting: Run your apps in multiple geographic locations to serve users faster and reduce latency
• Latency-first architecture: Ideal for APIs, streaming services, collaborative tools, and edge-native workloads
• Docker-native support: Bring your own Dockerfile or use the built-in builder to deploy containerized applications
• Persistent storage: Use volumes for apps that require data storage, like databases or file systems
• Full control over clusters: Advanced developers can configure deployments with regional fallbacks, service mesh, and multi-instance scaling
• Custom regions and scaling policies: Fine-tune your infrastructure to meet specific user distribution and performance needs

Limitations:

• Not beginner-friendly: Requires CLI-based setup, Docker familiarity, and some infrastructure knowledge
• Manual configuration: Compared to no-code or low-code platforms, Fly.io involves more setup steps and less visual tooling
• Less abstracted experience: You’re responsible for managing deployments, containers, and scaling logic, which might be too complex for solo devs or small teams without DevOps background

If you’re deciding whether edge deployment fits your architecture and team’s DevOps capacity, the full breakdown covers infrastructure requirements, CLI overhead, and real-world use cases.

5. Qovery

Best for: Teams that want the power of Kubernetes with a streamlined developer experience and GitOps-style deployment

Overview: Qovery is a managed deployment platform built on top of Kubernetes. It bridges the gap between infrastructure complexity and developer productivity by providing a clean interface and automated workflows, while still leveraging the full capabilities of Kubernetes under the hood. Qovery is particularly attractive for teams adopting microservices, containerized workflows, or transitioning to Kubernetes but lacking the time or expertise to configure it manually.

It supports Git-based deployments, preview environments, and environment isolation, making it suitable for fast-paced dev teams and growing SaaS startups. Qovery provides built-in integrations with databases, storage, monitoring tools, and supports staging, production, and ephemeral environments out of the box.

Key strengths:

• Kubernetes-level control with a simplified experience: Teams can deploy and scale services with Kubernetes-grade resilience without writing Helm charts or YAML
• GitOps-native workflows: Automatically builds and deploys apps on code pushes, with real-time status updates and logs
• Preview environments per pull request: Test features in isolation before merging, ideal for collaborative teams and CI testing
• Support for multi-service architecture: Easily manage services, databases, and background jobs across environments
• Built-in DevOps tooling: Offers integrated observability, scaling, secrets management, and network configuration
• Runs on your own cloud: Supports AWS, Azure, and GCP, giving teams flexibility and compliance control

Limitations:

• Slower onboarding curve: While simpler than pure Kubernetes, Qovery still requires some ramp-up time to understand its model and environment setup
• Partial abstraction: For advanced use cases, teams may still need to understand Kubernetes concepts like namespaces, pods, and ingress rules
• Best suited for mid-sized or technical teams: Solo developers or small non-DevOps teams might find platforms like Render or Kuberns faster to adopt
• Pricing varies based on cloud provider and workload: Teams deploying on their own AWS or GCP account must also monitor usage and infra costs separately

Qovery offers a middle ground between full Kubernetes complexity and the ease of Heroku-style platforms. It works best for growing teams with technical resources who want flexibility without reinventing the wheel.

For teams weighing whether Kubernetes abstraction is the right fit for their workflow and team size, the detailed breakdown covers onboarding complexity, pricing, and production readiness.

6. Vercel

Best for: Frontend teams building with React, Next.js, or static site generators who prioritize speed, simplicity, and collaboration

Overview: Vercel is a cloud platform optimized for frontend development. Originally built by the creators of Next.js, it has evolved into a go-to solution for modern frontend teams looking to deliver fast, performant user experiences with minimal configuration. Vercel offers zero-config deployments, global CDN distribution, and real-time collaboration features, making it a great fit for teams working on marketing sites, frontend UIs, eCommerce storefronts, and JAMstack-based projects.

It provides automatic previews for every Git pull request, allowing teams to review changes in real time. Built-in analytics, image optimization, and edge functions further enhance performance and user experience at scale.

Key strengths:

• Global CDN with edge caching: Delivers assets and dynamic pages from servers closest to the user, improving load times and reducing latency
• Seamless Next.js integration: Vercel natively supports advanced features like Incremental Static Regeneration (ISR), Middleware, and Server Components for Next.js apps
• Zero-configuration deployments from GitHub, GitLab, or Bitbucket: Push code to a branch and preview instantly
• Preview deployments for every PR: Share live URLs for collaboration, QA, and stakeholder feedback
• Built-in performance optimization: Automatic image compression, smart routing, and Lighthouse metrics built into the dashboard
• Supports static and dynamic pages: With support for edge functions and serverless functions for API routes

Limitations:

• Backend limitations: Vercel is not built for complex backend services, persistent processes, or long-running jobs. Developers often pair it with a separate backend hosted elsewhere (like Supabase, AWS Lambda, or an external database provider)
• Pricing for dynamic workloads: Serverless function usage, edge middleware, and bandwidth can lead to unpredictable costs as apps scale
• Not ideal for full-stack ownership: Vercel’s focus is heavily frontend-centric. Teams looking for end-to-end infrastructure control, including databases, background jobs, or custom infra, may find it limiting
• Limited observability tools: Logs and monitoring exist, but they’re minimal compared to platforms focused on backend or full-stack workflows

Vercel works best for frontend-heavy projects that need speed, simplicity, and great DX. But for teams building full-stack or backend-intensive applications, a platform like Kuberns offers more backend support and infrastructure control.

For teams assessing whether a frontend-scoped platform covers their full deployment needs, the breakdown covers backend limitations, pricing at scale, and full-stack alternatives.

Why Consider Alternatives to DigitalOcean in 2026?

DigitalOcean remains a popular choice for virtual private servers (Droplets), managed databases, and Kubernetes clusters. It’s known for its developer-friendly UI and competitive pricing for basic compute. But in 2025, the needs of developers and startups have evolved, and so have the expectations from modern cloud platforms.

Many teams now face challenges with DigitalOcean, such as:

• Fragmented workflows: Using Droplets for compute, separate services for databases, and third-party tools for CI/CD adds unnecessary complexity.
• Manual infrastructure management: Even with managed options, users often need to configure firewalls, set up monitoring, manage backups, and handle security updates manually.
• Limited automation: Teams still need to script deployments, manage environment variables manually, and create custom pipelines to support multi-service or microservice architectures.
• Unpredictable pricing: Add-ons like load balancers, snapshots, additional bandwidth, and monitoring can quickly inflate monthly costs, especially for scaling applications.

As a result, many developers are seeking a more integrated, automated, and scalable alternative, something closer to a fully managed Platform-as-a-Service (PaaS). They want to focus on writing and shipping code, not maintaining infrastructure.

As we move into 2026, modern teams want more than basic infrastructure. They’re looking for fully managed platforms that streamline deployment, remove DevOps overhead, and offer built-in features like autoscaling, observability, CI/CD, rollbacks, and staging environments, without complex setup.

In short, developers don’t want to stitch together tools anymore. They want one platform that handles build, deploy, scale, and monitor without extra setup or unexpected complexity.

That’s exactly what Kuberns is built for. A complete platform that lets you ship production apps in minutes, not days.

Why Teams Choose Kuberns Over DigitalOcean?

The difference between Kuberns and DigitalOcean isn’t just about features or pricing. It’s about where the operational responsibility sits.

With DigitalOcean, that responsibility always stays with your team. You provision the server, configure the pipeline, define the scaling rules, set up monitoring, manage backups, and respond when something breaks. The platform gives you the building blocks. What you build with them and how you maintain it are entirely up to you.

Kuberns flips that model. You connect your repository, and the platform’s agentic AI engine handles everything from that point, stack detection, build configuration, environment provisioning, deployment, scaling, and recovery. The infrastructure decisions don’t get delegated to a better dashboard. They get removed from your workflow entirely.

Here’s what that looks like side by side:

On DigitalOcean: Create a Droplet → install dependencies → configure Nginx → set up a CI/CD pipeline in a separate tool → define scaling rules → configure monitoring with a third-party integration → manage SSL certificates → handle backups → repeat for every environment.

On Kuberns: Connect your GitHub repository → set environment variables → deploy. The agentic AI platform detects your stack, builds the image, provisions the environment, runs health checks, deploys your app, and monitors it continuously — without a single infrastructure decision from your side. 

The full feature-by-feature breakdown is covered on the Kuberns vs DigitalOcean comparison page. Teams choose Kuberns specifically because:

Deployment responsibility is removed, not just reduced: No pipelines to wire up, no YAML files to maintain, no infrastructure tasks sitting in the backlog waiting for someone with DevOps knowledge to action them.

Unlimited team collaboration with no per-user pricing: DigitalOcean’s model is account-based. Kuberns supports unlimited users on the same project without per-seat charges stacking up as the team grows.

The workflow stays simple as the application scales: The same one-click flow that works for your first deploy scales to production traffic without a platform migration or a DevOps hire.

Cloud costs are optimised by default. Most teams report around 40% lower infrastructure costs compared to managing equivalent setups on DigitalOcean without any manual cost optimization effort.

Who Should Use Kuberns?

• Early-stage startups that need production-grade infrastructure from day one but don’t have a dedicated platform engineer. With Kuberns, a small founding team can deploy, scale, and monitor a production app with the same reliability a larger team would achieve with a full DevOps stack.
• Growing development teams spending too much time on failed deployments, pipeline maintenance, and scaling incidents instead of building products. If infrastructure issues are showing up regularly in sprint retrospectives, that’s the signal it’s time to switch.
• Agencies and freelancers managing multiple client projects simultaneously. Kuberns’ one-click deployment model and pre-built stack templates make it straightforward to maintain a consistent, repeatable workflow across projects without custom infrastructure setup for each client.
• Teams actively migrating off DigitalOcean who want to replace fragmented tooling, separate CI/CD, separate monitoring, and separate scaling config with a single platform that handles all of it automatically. The step-by-step DigitalOcean to Kuberns migration guide covers the full process, from backing up your existing setup to going live on Kuberns with minimal downtime.
• Developers building AI-powered or multi-service applications where infrastructure complexity compounds quickly. Kuberns’ automated environment detection and intelligent scaling handle the orchestration overhead that these workloads introduce, with no custom configuration required per service.

Ready to Make the Switch?

If you’re still configuring pipelines, managing Droplets, and wiring together monitoring tools manually, that means you are wasting both time and money on things that can be completely automated.

Kuberns’ agentic AI engine replaces that entire workflow. Connect your repository, and it handles stack detection, deployment, scaling, and recovery autonomously, the same way a senior DevOps engineer would, running continuously in the background, without the headcount cost.

The DigitalOcean to Kuberns migration guide covers the full switch from your first backup to a live production deploy with zero infrastructure reconfiguration required.

Start with $14 in credits for just $7. Enough to run your app for 30 days and experience what AI-managed deployment actually feels like.

Deploy on Kuberns with Agentic AI

DigitalOcean Alternatives Frequently Asked Questions

Q: What is the best DigitalOcean alternative in 2026?

If you need a fully managed platform that removes deployment and DevOps overhead entirely, Kuberns is the most complete option in 2026. It’s the only platform built on an agentic AI engine that handles your entire deployment lifecycle automatically, from stack detection to scaling and recovery, without any manual configuration.

Q: What is the cheapest DigitalOcean alternative?

For raw compute price-performance, Hetzner Cloud is hard to beat, particularly in Europe, where a plan with 2 vCPUs, 8GB RAM, and 160GB storage runs around €6/month, dramatically more than DigitalOcean or Vultr at the same price point. Vultr starts at $2.50/month for entry-level compute. For teams where the higher cost isn’t the server bill but the engineering hours spent managing infrastructure, Kuberns’ compute-only pricing with no per-user fees and around 40% lower costs than equivalent AWS setups may represent better overall value.

Q: Which DigitalOcean alternative is best for startups?

Startups without a dedicated DevOps engineer are best served by a fully managed platform rather than raw infrastructure. Kuberns is purpose-built for this.

Q: Can I migrate from DigitalOcean without changing my code?

Yes. If your codebase is on GitHub, migrating to Kuberns requires no code changes. You connect your repository, configure environment variables, and deploy. Kuberns’ agentic AI detects your stack and configures the build pipeline automatically. The full step-by-step process is covered in the DigitalOcean to Kuberns migration guide, including how to back up your existing setup, restore application data, and go live with minimal downtime.

Q: Is Vultr better than DigitalOcean?

For raw compute performance and global reach, Vultr has an edge, 32+ data centre locations versus DigitalOcean’s 15, high-frequency compute instances, and a starting price of $2.50/month. For managed services, developer documentation, and community resources, DigitalOcean has a more mature ecosystem. Both are IaaS providers that require manual infrastructure management; neither removes DevOps overhead the way a fully managed platform does.

Q: What is the best DigitalOcean alternative for full-stack app deployment?

Kuberns is the strongest choice for full-stack deployment. It supports both frontend and backend frameworks, automates CI/CD, includes logs and monitoring, handles staging environments, and offers instant rollbacks, all without Docker or YAML configuration. For teams comfortable with some manual setup, Render supports full-stack apps with good database and worker support. 

Q: Does Kuberns replace DigitalOcean Droplets and Kubernetes clusters?

Yes. Rather than replacing Droplets with equivalent VMs or Kubernetes clusters with a managed K8s service, Kuberns replaces the entire infrastructure management layer. You don’t provision servers or manage clusters directly. The platform’s agentic AI engine provisions and manages all the underlying compute, networking, and orchestration automatically. Teams migrating from DigitalOcean don’t rebuild their infrastructure on Kuberns. They connect their code repository and let the platform handle the rest. See the full Kuberns vs DigitalOcean feature breakdown for a detailed comparison

Q: Why are developers switching away from DigitalOcean in 2026?

Many developers now prefer platforms that offer a fully managed experience. While DigitalOcean provides solid infrastructure, it still requires manual setup for CI/CD, scaling, monitoring, and environment management. Teams are choosing alternatives like Kuberns to reduce DevOps overhead and move faster.

Q: Which platform includes built-in CI/CD and monitoring tools?

Kuberns includes CI/CD, staging, logs, and monitoring tools without requiring external integrations. Render also supports CI/CD, though some configuration may be required.

Q: Is Kuberns the same as Kubernetes?

No. Kuberns simplifies the deployment process without the complexity of Kubernetes. You don’t need to manage clusters, YAML, or Helm charts Kuberns handles all that internally.