Skip to main content
Open console

Projects

One application, its settings, and what changing them does.

8 min read

A project is one application. It holds the repository the code comes from, the environments that run it, and the settings that decide what those environments are allowed to be.

Creating one

You are asked for a name only. The project belongs to the team the console is showing, and cannot be moved to another team afterwards. Its machine name is generated for you and is permanent: it reaches hostnames, paths and backup prefixes. Support level and uptime promise are not asked here.

Starting a project, and everything on the Configure page, takes the Admin role or above.

An unconfigured project cannot be built. Until it is configured, every link to it goes to the Configure page.

Configure

One page, worked down in steps, with the total beside it. Every choice reprices immediately, so the number in the summary is the number you will be billed.

  1. Application — what the code is.
  2. Plan — dedicated or shared.
  3. Shape — how many machines, and what each one does.
  4. Location — the region, the datacentre in it, and the kind of machine. The region narrows the datacentres to the ones there. The page opens on your billing country where there is a datacentre in it, and on its part of the world otherwise. Prices vary by datacentre, so the machines below switch when the datacentre does.
  5. Services — what runs beside the site, and the machines it runs on.
  6. Edge — the origin bandwidth your machines include, more of it if you need it, and a CDN in front. See Plans.
  7. Add-ons — the staging and development environments beside production, and longer backups.
  8. Configure project — support, the uptime promise, custom domains and the team.
  9. Billing period — monthly, quarterly or yearly.

A site joining a shared machine you already have skips what that machine has already decided: its shape, its location, its edge, and its support, uptime and billing period.

Nothing is bought until you build an environment.

Your configuration is checked when you press the button, and again on the last page of checkout, before you pay:

  • the machines are still sold and in stock where you chose;
  • the provider has room for them;
  • your team is within its limits.

Every machine the order buys counts towards the team's machines, the one your preview environments share included. Its production environment counts towards the team's environments. If something has changed in between, checkout says what, nothing is charged, and Change the configuration opens the configurator on your choices.

Support and uptime

Standard is included. The paid levels are priced as a share of what your machines cost, and support has a minimum as well. The configurator quotes the figure before you agree to it, and the price list has the shares.

Level Support response Uptime
Standard 4-hour best-effort on urgent tickets 99.9% committed
Advanced 60-minute guaranteed on urgent tickets 99.95% committed
Premium 30-minute guaranteed on urgent tickets 99.99% committed

Support counts every machine, extras included. The uptime price counts the machines carrying the site, not the extras: the promise does not cover them.

The response times are for urgent tickets: a site that is down. Everything else is answered too.

Best effort means we work to four hours and owe you nothing if we miss. Guaranteed means we have agreed to the figure.

Uptime is a commitment at every level, Standard included, with service credits when it is missed. In a 30-day month that is about 43 minutes of downtime at 99.9%, 22 minutes at 99.95%, and 4 minutes at 99.99%.

A shared plan is always Standard uptime and the field cannot be changed: Advanced and Premium are sold on a dedicated plan.

Service credits

Where a month misses the figure committed to, a share of that month's invoice comes back. The share is worked out from the Monthly Availability Rate. It is a percentage of what was invoiced for the resources that missed: a database machine that was down does not refund the CDN that served alongside it.

Monthly availability Standard Advanced Premium
Below the committed figure, at or above 99.0% 5% 10% 15%
Below 99.0%, at or above 95.0% 10% 25% 35%
Below 95.0% 20% 50% 50%

Premium support and the Advanced uptime SLA are sold on a three-month billing period or longer, and the Premium uptime SLA on a yearly one.

Level Condition
Advanced uptime SLA Sold on any machines, one or many
Premium uptime SLA Sold on machines with reserved cores, every machine carrying the site, and with Advanced support or above
Premium support Not sold with an entry-line machine

A site on the Premium uptime SLA keeps reserved cores when its machines are resized or added to.

Storage

The machine's disk is divided between what fills it: the database, a search index, a queue, public files, private files, and a reserve for mounts. The configurator opens with this split and lets you change each figure:

  • On the machine holding the files, the database takes a quarter and the files the rest.
  • A search index or a queue added beside them takes its share from the files, never from the database.
  • On the flexible and dedicated shapes every machine has a storage box of its own. A machine carrying two services that fill a disk, say the database beside a search index, halves it between them. Either can still be given a disk of its own, and what stays takes the whole machine.
  • Mounts start at nothing. They are the extra directories your application names in vallic.yaml, and whatever you reserve here is shared between them once they are named.

A bucket that will not fit, or that you expect to grow, can be given a disk of its own right there, from 10 GB in 5 GB steps to 50 GB, 10 GB steps to 100 GB, then 50 GB steps to 1 TB: one disk for the public files, one for the private files (the mounts go with them), one for search, one for the queue. The database always stays on the machine. Disks are made once the machine exists and are mounted before the first deploy, so nothing has to move. The environment's Storage tab shows each bucket against its budget.

Resizing a machine later does not change any of this. The machine's own disk stays the size it was, so the budget and the disks you bought stay as they are. What you moved onto its own disk stays there. To add room on the machine, buy a disk: a bigger machine does not add any.

Billing period

Monthly by default. A quarter or a year paid ahead is discounted, the same for every plan. It is chosen last on the configurator.

Changing a project

Before any machine is built, everything is still a choice on the Configure page: the plan, the shape, the application, the support level, the uptime promise.

Once it is built, the project's configuration page has two cards, each with its own Change:

  • Project — the name, the group it is listed under, the default branch, and the application until something has deployed.
  • Plan — the plan, the shape and the billing period, which changes at renewal.
  • Commercial terms — a card for each part, each with its own Change: support and uptime, preview environments, bandwidth and the CDN, custom domains, backups, and autoscale where the machines are on cloud native compute. Each dialog quotes the change before you agree to it. Anything you add is available at once and charged for the rest of the period. Anything you reduce stays yours to the end of the period you have paid for and comes off the next invoice.
Setting After it is built
Plan Fixed
Shape Fixed — within Flexible the Resources tab still moves services onto machines of their own
Application Changeable until the first release is serving, then fixed
Support level Change any time
Uptime promise Change any time
Machine sizes Change any time, up, and down on some kinds

Changing a plan or a shape moves your data to different machines. Changing the application under a running site runs a different container with different code. All three are migrations support does for you. See Plans and Shapes.

Groups

A team with several projects can list them under groups: a client's sites, a brand's, or a shop and the API behind it. Groups change how the console lists your projects and nothing else. A project's machine name, addresses, environments, access and bill are the same whichever group it is in, or none.

  • The Projects page shows the groups first, a card each: the projects in it, how many there are, and whether their production environments are running. Every project is still listed below.
  • The dashboard shows the same cards above your newest projects.
  • A group's page lists its projects, and under them each project's environments with the machines each one runs on.

An Admin or the Owner makes, renames, orders and removes groups, from Manage groups on the Projects page. Removing a group never removes a project. Anyone who can rename a project puts it in a group, or takes it out, in the Project card's Change dialog on its configuration page. A project is in one group at most.

Next

Need a hand?

Open a ticket from Support in the console. We answer on the ticket.

Open the console How support works