Bytemark vs Cloud Foundry

What Bytemark is

Bytemark is a UK hosting brand acquired by iomart. Its still-published service and documentation pages describe cloud servers from £10 per month, dedicated and managed hosting, UK facilities, an API and the open-source Symbiosis server stack. However, the original BigV cloud platform stopped receiving support on 30 April 2023 and customers were directed toward iomart's OnApp platform. The legacy website and price list remain reachable, so a new buyer should confirm current ordering, contract, platform and support status directly rather than treating every historical claim as a current offer.

What Cloud Foundry is

Cloud Foundry is an Apache-licensed, openly governed application-platform ecosystem. Developers push supported application code through the cf CLI and platform API; operators provide routing, buildpacks, container scheduling, identity, logs, quotas and service integrations. The software has no license fee, but a production foundation still requires infrastructure, load balancers, DNS/TLS, databases, blob stores, monitoring, backups, updates and skilled operations—or a separately priced commercial distribution or managed provider. Certification verifies required core components for a specific program year; it is not the same as generic API compatibility or an uptime guarantee.

What Bytemark is built to do

UK hosting infrastructure

Published services span cloud servers, dedicated systems, racks and managed hosting.

API and CLI

Legacy cloud documentation supports programmatic account, image and server operations.

Symbiosis

Provides an open-source Debian-based stack for websites, mail, databases, firewalling and updates.

iomart migration path

Official documentation directs unsupported BigV workloads toward iomart's OnApp platform.

What Cloud Foundry is built to do

cf push workflow

Stages supported source or artifacts with buildpacks and schedules application instances.

Organizations and spaces

Scopes applications, routes, services, quotas and role-based access for multiple teams.

Service broker model

Provisions and binds managed services through the Open Service Broker API.

UAA identity

Provides OAuth-based platform identity with configurable LDAP and SAML federation.

Choose Bytemark if

• Existing dedicated, rack or managed-hosting customers validating their continuing service
• Legacy BigV owners who need the official migration constraints and destination context
• Teams interested in maintaining the open-source Symbiosis stack independently

Skip Bytemark if

• A new production deployment would rely on the unsupported BigV platform
• The purchase requires fully self-service current prices and terms without sales confirmation
• The team cannot test application, network, backup and billing behavior after migration

Choose Cloud Foundry if

• Large application portfolios that conform to buildpack or supported container workflows
• Organizations prioritizing consistent developer experience across infrastructure choices
• Internal platforms with dedicated owners for upgrades, security, observability and disaster recovery

Skip Cloud Foundry if

• The organization has only a few simple services and no platform-operations capacity
• Applications require privileged hosts, unusual kernels or infrastructure-level control
• The selected distribution has no verified lifecycle, support, certification or backup responsibility

Bytemark: pros & cons

• Developer-oriented heritage: Published documentation covers API and command-line server management.
• UK infrastructure focus: Bytemark materials describe facilities and network presence in several UK locations.
• Transparent legacy documentation: Pricing, support processes, network design and migration notices remain publicly accessible.
• Open hosting stack: Symbiosis is a Bytemark-developed Debian-based environment with automated hosting administration.
• Platform transition risk: BigV became unsupported in 2023 and the recommended destination is an iomart platform.
• Current-sales ambiguity: Reachable marketing and pricing pages contain legacy claims that may not represent a new order today.
• Self-managed responsibility: Cloud-server users still own application, operating-system and restore readiness unless management is contracted.
• Migration can change behavior: Platform, networking, backup and billing details must be revalidated on the destination service.

Cloud Foundry: pros & cons

• Developer abstraction: A consistent cf push workflow hides much of the infrastructure configuration from application teams.
• Open governance and source: Foundation projects use open contribution, design and governance processes.
• Infrastructure choice: Cloud Foundry can be deployed on multiple IaaS environments or consumed through commercial offerings.
• Platform controls: UAA identity, RBAC, orgs, spaces, quotas, routing, logs and service brokers provide multi-team governance.
• Free software has real operating cost: Production topology, infrastructure, upgrades, security and recovery need a platform team.
• Provider experience varies: Buildpacks, services, extensions, support, certification and pricing differ among distributions.
• State remains external: Databases and bound services need their own durability, credential and restore strategy.
• Not general compute: The opinionated application model is a poor fit for workloads needing unrestricted hosts or unusual system dependencies.