Last updated 4 November 2026

Terms of Service

These terms govern your use of Silly Development. By creating an account or using the service you agree to them. If you do not agree, please do not use the service.

Who we are

Silly Development is operated by an individual sole trader based in the United Kingdom. Where these documents say "we" or "us", they mean that operator.

You can reach us at [email protected] for anything relating to your data or these terms, and at [email protected] to report misuse of the service.

What we provide

We provide hosting for small, long-running Node.js, Python, Bun and Ruby projects: bots that connect out to a service such as Discord, Minecraft, Telegram or WhatsApp, small web apps and APIs, background workers, scheduled scripts and similar programs. Every free server receives a fixed allocation: 25% of a CPU core, 256 MB of memory, and 512 MB of disk. We support Node.js, Python, Bun and Ruby.

We host your project and nothing else. We are not a general virtual server, and we do not host game servers except as our Acceptable Use Policy allows. A web app or API is reachable at the address and port shown in your panel; we do not provide a domain name or an HTTPS certificate for it. Where we describe a platform, that describes what your code may connect to, not something we operate or have any relationship with.

The free service is not a trial and not a cut-down version of something better. The allocation above is not reduced, time-limited, or throttled to push you toward paying, and it did not change when we introduced a paid plan. You never have to pay us anything.

Where we offer them, each account may also create a limited number of free MariaDB and PostgreSQL databases, each with a fixed disk quota shown in your panel. A database belongs to your account rather than to a server. Optional paid database plans give a database more room for a monthly fee, as described in "Paid databases" below. Everything in these terms about your code and your data, acceptable use, availability and suspension applies to your databases as it does to your servers.

There are optional paid plans, which give a server more of that allocation for a monthly fee. They are described in "Paid servers" below. Everything else in these terms applies to free and paid servers alike unless that section says otherwise.

There is no guarantee attached to a service you are not paying for — see "Availability" below.

Account credit

Your account can hold a credit balance. Credit comes from rewards in our referral programme, from refunds you choose to take as credit, and occasionally from us. It is not money: it has no cash value, it cannot be paid out, refunded to a card or transferred to another account, and it can only be spent on your own account. Your balance and every change to it are shown on your billing page.

Credit is spent on your own bills only. If it covers a whole month of a paid server, you can buy the server with credit alone, without a card. That plan then renews from your credit each month while the balance covers it. If it does not, we email you, and you can renew in cryptocurrency instead; otherwise the server is paused 24 hours after its paid month ends and moves to the free plan seven days after, as described for crypto plans above. A promotion code cannot be used on a purchase paid with credit; pay by card or crypto to use one.

Credit can also be taken off a crypto payment. If your credit does not cover the whole payment, enough is left to pay in crypto that the payment is worth sending (currently at least 25p). Credit taken off a crypto payment that is never paid is given back.

If you pay for a server or database by card, spare credit is moved to your balance with our payment provider, Stripe, where it is taken off your next card bills before your card is charged. Credit kept for any plan you pay for with credit stays in your account. Once credit has moved to Stripe it stays there and is used on card bills only.

A plan paid for with credit can be ended early, with the unused time returned to your credit less the 5p fee, under the same one-per-30-days allowance. Your right as a UK consumer to cancel within 14 days, described in "Paid servers", is not affected.

We may correct a balance that is wrong, and take back credit that was given in error, through a reward that turned out not to qualify (such as for a refunded or disputed payment), or through misuse of the service or the referral programme. A balance can go below zero as a result; later credit pays that off first. If your account is closed, any credit on it ends with it.

We may change how credit can be spent, or stop offering it. If we stop offering it, we will tell you at least 30 days before, and credit already on your account can still be spent on your bills during that time.

Eligibility

You must be at least 13 years old to use Silly Development. If the law where you live sets a higher age for consenting to online services, or a platform your project connects to sets a higher one, that higher age applies to you.

You must not use the service if you have previously been permanently banned from it.

To buy a paid server or a paid database plan you must be 18 or over, or have the permission of a parent or guardian who agrees to pay for it.

Your account

You are responsible for everything that happens under your account. Keep your password to yourself, and enable two-factor authentication if you can.

Give us accurate registration details. One person should hold one account: creating additional accounts in order to stack resource allocations is a breach of these terms and of our Acceptable Use Policy.

An API key that has not been used for 90 days is deleted, and we email you before that happens. You can make a new one at any time.

Tell us promptly at [email protected] if you believe someone else has accessed your account so we can lock it down. We will not be liable for any loss or damage arising from your failure to do so.

Your code and your data

Your project, its source code, and its data are your responsibility. We do not guarantee that it will work or be preserved.

You keep every right you have in your project. You give us permission to store, copy, run, back up and check it, only as far as that is needed to provide the service and enforce these terms. That permission ends when the project is deleted from our servers.

To keep the service safe for everyone on it, we run automated checks on what is hosted here, including the files on your server and how much of its resources it uses. Those checks can suspend a server on their own when something looks like a breach of the Acceptable Use Policy. If you think one got it wrong, reply to the notice and a person will look at it. We do not describe how the checks work in detail, because doing so would mainly help people get around them.

A person reads your files or console output only when that is needed to investigate something the automated checks or an abuse report have flagged, or to help you with a problem you have asked us about. We do not otherwise access them, and we do not share them with anyone else except as the Privacy Policy describes.

If your project has users of its own, such as the members of a server your bot is in or the people signing up to your web app, you are responsible to them for it. That includes keeping their data secure, handling it lawfully, and providing any terms or privacy notice your project needs. We provide the hosting and are not a party to that relationship.

You are responsible for having your own backups. We may keep backups for operational reasons, however these are not guaranteed to be complete or restorable, and we do not provide a way for you to access them. Any such backup is deleted within two weeks of being taken. That includes your databases: apart from the copy kept for a few days after you move one to another version, we do not back them up for you.

Acceptable use

Your use of the service is subject to our Acceptable Use Policy, which forms part of these terms. It sets out what you may not run on our infrastructure.

Availability

We aim to keep the service running as much as possible. We do not, however, offer a service level agreement or any uptime guarantee. That is true of paid servers and paid databases as well: paying for more memory or more disk buys you exactly that, not a promise about uptime, and we would rather say so than imply otherwise.

The service may be unavailable for maintenance, because something has broken, or because we have decided to stop offering it. We will give reasonable notice when we decide to shut it down. If we withdraw the service, or stop offering paid plans, we will refund the unused part of anything you have paid us.

Suspension and termination

We may suspend or terminate a free account or a free server whenever we feel the need to, for any reason. Subject to the "Liability" section below, we will not be liable for any loss or damage arising from that.

We will only suspend or terminate a paid server or a paid database for a valid reason: a breach of these terms or the Acceptable Use Policy, non-payment, a legal requirement, a risk to the service or its users, or our withdrawing the service or the paid plan.

If possible, we will warn you first and give you a chance to put things right. Serious cases — anything illegal, anything that puts other users at risk — may be actioned immediately and without notice.

Where we suspend or terminate a paid server or a paid database for any reason other than your breach of these terms or the Acceptable Use Policy, we will refund the unused part of the month. Suspension for non-payment is dealt with in "Paid servers" and "Paid databases" above and is not a termination.

A free server that is never used in the 7 days after it is created is deleted, so that somebody else can have the room. Starting it or opening its console counts as using it, and we normally email a warning a couple of days beforehand.

For the same reason, a free server that has been left idle is deleted: after 30 days if it holds no files, or after 90 days if it does. A server is idle while it has not run at all, not even for a moment, and nobody with access to it has done anything with it in the panel. We email you at least a week before it is deleted, with a link to keep it, and keeping it starts the clock again.

When somebody reports one of your servers to us, a member of staff looks at the report. If you can put it right, we may email you saying what needs to change and by when. Reply to that email to tell us what you did. Missing the date does not suspend anything by itself: staff look at the server again and decide.

We never tell the person who reported your server who you are, which server it was, or anything else about your account. They can see whether their report is still open and anything we choose to tell them about the outcome, nothing more.

A suspended server may be deleted. If it is going to be, we will email you the date before it happens.

You may close your account at any time from your account settings, or by emailing us at [email protected]. It is deleted a week after you ask, and until then you can call it off from the link in the email we send you. While a paid server or paid database is still being paid for, end its plan first. When the account is deleted, all its data goes with it, including your files and databases, as the Privacy Policy describes. We may retain a minimal record of accounts terminated for serious abuse, in order to enforce the ban.

The platforms your project connects to

Discord, Minecraft server operators, Telegram, WhatsApp and anyone else your code talks to are nothing to do with us. We have no relationship with them, no influence over them, and no visibility into their decisions. Their terms apply to you separately from ours, and it is your responsibility to know them and to keep to them.

You are responsible for any account, token, number or credential your project uses. If one of those platforms restricts, suspends, bans or deletes an account, a number or a bot of yours, that is a matter between you and them. We are not liable for it, we cannot appeal it for you, and we cannot recover anything lost with it.

This matters most for automation a platform does not officially support. Where we host something of that kind we say so on the page for it, and we say plainly that we do not recommend it. Choosing to run it anyway is your decision and the consequences are yours.

No warranty

The service is provided "as is" and "as available", without warranties of any kind, to the fullest extent the law allows. We do not warrant that it will be uninterrupted, secure, or free from error, or that any data stored on it will be preserved.

Liability

Nothing in these terms limits or excludes our liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be limited. If you are a consumer, nothing in these terms affects your statutory rights.

Subject to that, we are not liable to you for loss of profit, loss of business, loss of data, or any indirect or consequential loss arising from your use of or inability to use the service. Where the service is provided to you free of charge, that is the whole of our liability. Where you are paying for a server or a database, our total liability to you for any claim is limited to the amount you have paid us for that server or database in the twelve months before the claim arose.

That includes the loss of any third-party account, number, token or bot used by, or affected by, something you ran here. See "The platforms your project connects to" above.

Changes

We may update these terms. Where a change materially affects you we will give notice through the panel or by email before it takes effect.

If you are paying for a server or a database and do not accept a change that materially affects you, you may cancel before it takes effect and we will refund the unused part of the month, without the fee described in "Paid servers". Otherwise, continuing to use the service after a change takes effect means you accept the revised terms.

Governing law

These terms are governed by the law of England and Wales, and disputes shall fall to the courts of England and Wales. If you are a consumer resident elsewhere in the UK, you may bring proceedings in your local court instead.