Your data is located entirely within the UK and is subject only to UK law.
We own and operate every layer of our stack: hardware, software, network and IP space.
Our datacentre infrastructure is powered entirely by renewable sources.
Your data is yours and unlike hotel california you can easily leave anytime.
 
            Brightbox have been exceptional since the day that we signed up. Incredibly responsive support and uptime so good that I don't even think about it.
 
            Really love using the Brightbox control panel to manage our cloud servers, ips, firewall and cloud storage. Much easier to use than Amazon AWS. Also customer support is just excellent, with incredible response times.
 
            I’m not really an ops-guy, but the simplicity of the interface and the helpful Brightbox team made me think that I could do it. It’s been 5 years!
 
            We have used Brightbox for the last 8 years and have been grateful for the rock solid infrastructure, expertise and thoughtful support they have provided. Thank you!
# Create a server
$ curl https://api.gb1.brightbox.com/1.0/servers \
    -X POST \
    -H 'Authorization: Bearer 414028a4b75139fc1b03b51dc294d1b4c591d666' \
    -H 'Content-Type: application/json' \
    -d '{"image":"img-xxxxx","name":"Test server from API"}'
{
   "resource_type" : "server",
   "id" : "srv-mcj3x",
   "created_at" : "2020-08-03T13:54:21Z",
   "console_token" : null,
   "started_at" : null,
   "cloud_ips" : [],
   "snapshots" : [],
   "name" : "Test server from API",
   ...
}$ brightbox servers create -n "Test server from CLI" img-xxxxx
Creating a 1gb.ssd (typ-w0hf9) server with image ubuntu-bionic-18.04-amd64-server (img-xxxxx)
 id         status    type     zone   created_on  image_id   cloud_ips  name
--------------------------------------------------------------------------------------------
 srv-zx1hd  creating  1gb.ssd  gb1-b  2020-08-02  img-xxxxx             Test server from CLI
--------------------------------------------------------------------------------------------require 'fog'
compute = Fog::Compute.new(
  :provider => :brightbox,
  :brightbox_client_id => "cli-xyzab",
  :brightbox_secret => "some_secret"
)
zone = compute.zones.first
compute.servers.create(:zone_id => zone.id, :image_id => 'img-s0jtd')func main() {
        apiUrl := "https://api.gb1.brightbox.com"
        // Setup OAuth2 authentication
        conf := clientcredentials.Config{
                ClientID:     "cli-xxxxx",
                ClientSecret: "somesecret",
                Scopes:       []string{},
                TokenURL:     apiUrl + "/token",
        }
        oc := conf.Client(oauth2.NoContext)
    
        // Setup connection to API
        client, err := brightbox.NewClient(apiUrl, "", oc)
        // Get a list of servers
        servers, err := client.Servers()
        for _, server := range servers {
                fmt.Printf("id:%s name:%s\n", server.Id, server.Name)
        }
}$ docker-machine create -d brightbox \
    --brightbox-client cli-xyzab \
    --brightbox-client-secret some_secret
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
To see how to connect Docker to this machine, run: docker-machine env exampleterraform {
  required_providers {
    brightbox = {
      source  = "brightbox/brightbox"
      version = "~> 3.0"
    }
  }
}
provider "brightbox" {
  username = var.user_email_address
  password = var.user_secret_password
  account = var.account_to_work_on
}$ terraform init
Initializing the backend...
Initializing provider plugins...
- Finding brightbox/brightbox versions matching "~> 3.0"...
- Installing brightbox/brightbox v3.4.3...
- Installed brightbox/brightbox v3.4.3 (signed by a HashiCorp partner, key ID 86A01C78D276AC7C)
Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html
Terraform has been successfully initialized!
...apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app.kubernetes.io/name: brightbox-cluster-autoscaler
  name: release-brightbox-cluster-autoscaler
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: brightbox-cluster-autoscaler
  template:
    metadata:
      labels:
        app.kubernetes.io/name: brightbox-cluster-autoscaler
    spec:
      containers:
      - name: brightbox-cluster-autoscaler
        image: brightbox/cluster-autoscaler-brightbox:1.32.2
        command:
        - ./cluster-autoscaler
        - --cloud-provider=brightbox
        - --namespace=kube-system
        - --cluster-name=example.cluster.local
        - --logtostderr=true
        - --skip-nodes-with-local-storage=true
        - --stderrthreshold=info
        - --v=2
        envFrom:
        - secretRef:
            name: brightbox-credentials
        ports:
        - containerPort: 8085
          protocol: TCPOrbit is our highly available and durable object storage service. It’s at the centre of so many of our services at Brightbox: all Cloud Server and Cloud SQL ...
Read blog postToday we’re announcing support for version 17 of PostgreSQL in Cloud SQL. PostgreSQL 17 contains a number of new features and enhancements, including: N...
Read blog postAs part of our managed ops services we often need to share sensitive information such as passwords and keys with customers. GPG is commonly used for this kin...
Read blog post