Which machine, and what moves you up one.

THE FOUR

What each one is.

Your own hardware

Whatever you already have, or a machine you buy. 39 EUR a month covers the installing, the keeping current and being the person who is called. The machine is not our line item and its size is your decision, taken with us.

Ours · Small

2 cores, 4 GB, 40 GB. One system with a handful of people on it, or two quiet ones. Where most first deployments start and a good many stay.

Ours · Medium

4 cores, 8 GB, 80 GB. Several systems beside each other, or one that is busy. The size an organisation of a few dozen usually settles at.

Ours · Large

8 cores, 16 GB, 160 GB. A working stack with room in it, or one system with real load. Past this the answer is more machines rather than a bigger one.

The counts above are ours and are a judgement rather than a measurement: what a machine carries depends on what you put on it and how it is used. What we will not do is size it in a sentence on a web page and then hold you to it. The assessment is where a real number comes from.

WHAT MOVES YOU UP

Disk first, then memory, and only rarely the processor.

• Disk, almost always, and almost always before anyone expects it. A file store fills, a mail spool grows, a video library is measured in hundreds of gigabytes rather than tens, and backups need room beside the thing they back up
• Memory, when a second or third system moves onto the same machine. Each wants its own database and its own cache, and the sum is what runs out
• Processor, rarely, and usually only where video is being mixed or a model is being run. Most of what these systems do is waiting
• People, hardly ever on its own. Twice the headcount on a chat server is not twice the work; a hundred people and a thousand are the same machine far more often than anyone expects

Moving up is a planned maintenance job with a window agreed in advance, and the deployment goes across whole: the data, the configuration and the address. It is charged at the hourly rate like any other work, and nothing about the arrangement changes.

PRICE SHAPES

Its own machine

• Matrix
• Mail
• Nextcloud / Seafile
• Keycloak
• Forgejo / GitLab CE
• PostgreSQL
• Pipelines
• Proxmox VE
• Projects and tickets
• CRM
• Moodle

Setup once, then the monthly rate for where the machine stands.

PRICE SHAPES

Sized before priced

• Jitsi Meet
• BigBlueButton
• PeerTube
• Object storage
• Analytics store and reporting
• OpenSearch
• Local inference

The workload and required hardware are agreed before a price is quoted.

WHAT IT COSTS EITHER WAY

The figures, and where they live.

On your own hardware

39 EUR a month, whatever the machine is

On ours

From 69 EUR a month, by the size above

Setup

590 EUR once, invoiced before the work begins

Moving between sizes

110 EUR an hour, planned in advance

Tax

No VAT is added: we are not registered for it, so the figure shown is the whole figure.

The same rates apply across the service pages. Prices are per machine rather than per person. Moving up a size changes the machine charge.

WHAT IS AGREED IN TIME

The periods, and the clause each one comes from.

Sizing is a judgement and the table above says so. These are not judgements: they are the periods the contract holds both sides to, and they do not move with the size of the machine.

Before anything starts

An order becomes a contract when we confirm it in writing, and anything said before that is an estimate. Setup begins once the first invoice is paid and you have provided what the deployment needs: a domain, access to the machine where it is yours, and any directory we are asked to join. Clause 4.

A support request, standard

2 in 30 days, answered within 2 working days, included with the machine. Working hours, Monday to Friday, excluding public holidays: a request sent on Friday evening is answered on the next working day.

A support request, priority

4 in 30 days, answered within 8 working hours, at 199 EUR a month. The same working hours. Anything past either allowance is charged at 110 EUR an hour.

An invoice

Payable within 14 days. Setup once before the work begins, maintenance monthly in advance, and work outside the agreed scope quoted before it starts and invoiced when it is done. Clause 5.

A price change

At least 30 days before it applies to you, and never to a month already invoiced. Clause 5.

A change to these documents

At least 30 days before a material change applies, and you may end the contract before it takes effect. The date a version came into force is printed on the document, with every earlier date listed under it. Clause 14.

Notice to stop

1 month in writing, either way. No reason is required and there is no exit fee of any kind. Clause 13.

A breach

Either side may end it at once where the other commits a material breach and has not fixed it within 14 days of being told. Clause 13.

Your data after you stop

Personal data we hold for you as processor is deleted within 30 days of termination, sooner if you ask, unless the law requires us to keep it. Clause 13.

Cancelling as a consumer

Where you ordered as an individual rather than as an organisation, 14 days from the day the contract is made, and the refund within 14 days of your telling us, less the value of any work you asked us to begin inside the window. Clauses 4 and 5a.

Start and delivery dates are agreed in the written scope before the first invoice. Support is counted in working hours under clause 6 of the terms.

IF IT DOES NOT SUIT

Including the case where we sized it wrong.

Sizing is agreed against the systems, workload and capacity required by your organisation.

When the view turns out wrong the remedy is the ordinary one and not an argument: the deployment moves to another size as planned maintenance, in a window agreed in advance, and it goes across whole — data, configuration and address. It is charged at the hourly rate like any other work, nothing else about the arrangement changes, and clause 7 makes no performance promise for us to have broken.

If the answer is not to proceed

An assessment that ends in stay where you are is a finished piece of work, and the invoice is the same as one that ends in a build. That is the outcome we are paid for rather than the outcome we prefer, and it is why the assessment is priced small enough to commission before anyone is committed.

If the work is not what was agreed

Where you ordered as a consumer the Consumer Rights Act 2015 requires it to be carried out with reasonable care and skill and lets you require the work to be done again, or the price reduced; no contract can take that away and clause 5a says so. Where you ordered as an organisation, clause 12 limits our total liability in any twelve-month period to what you paid us in it, and nothing above that figure is promised.

If you want to leave

1 month's notice, either way, and the act of leaving costs nothing. You get the deployment as it stands — database, file store and configuration — rather than a farewell export, and access is withdrawn on request. Handover work is charged at 110 EUR an hour; leaving is not. Clause 13, and the leaving page in full.

If we would be the wrong supplier

Where a mainstream hosted product already does the job, nobody on your side will own the result, or the deciding factor is the lowest price this quarter, we would decline the work. We would rather lose it than find out in month three.

If something is broken

An outage is counted and never charged, on either support level. There is no availability promise behind that and clause 7 says so: what is promised is how quickly we answer, not that nothing will fail.

Every line above is in the terms of service, the data processing agreement or the leaving page, all three published in full before anyone is asked to sign anything. Where one of them changes it changes there first and here second, and the date it took effect is printed on the document.