Terms of use
Last updated 6 October 2026
These are the terms for using VibeStack, the vibecoding workspace for schools at vibestack.autobricks.ai, run by AutoBricks AI — a Singapore business and the agentic AI wing of Hexcore Labs.
Who agrees to this
The school or programme does, not the pupil. VibeStack is built for pupils aged 18 and below, who are not in a position to agree to terms of use. An account only exists because a teacher or administrator issued a signup code, and the school that issued it accepts these terms for everyone it admits.
If you are a pupil reading this: you do not have to agree to anything. Ask your teacher.
What VibeStack is
A place to build websites by describing them to an AI assistant, with a database, visitor sign-ups and publishing attached, and notebooks for working with data. It is a teaching tool. It is not a production hosting platform and should not be relied on as one.
Accounts and the signup code
There is no open registration. The signup code is the invitation, and whoever holds it can make an account — so it should be given out in a lesson and rotated afterwards, which an administrator can do in one click. Accounts are for one person. Passwords should not be shared.
Using it
Do not use VibeStack to:
- break the law, or help anybody else to;
- make anything that bullies, harasses, or impersonates a real person;
- make sexual content, or anything sexual involving a minor;
- attack, scan or overload this platform, another pupil’s work, or anybody else’s systems;
- get around the allowances, the sandbox, or the separation between accounts;
- store anybody’s personal data in a project database beyond what a lesson needs.
We can suspend an account or take a published site down if any of that happens. For a pupil account we tell the school rather than dealing with the pupil directly.
Who owns the work
The pupil does. Projects, files, notebooks and the data they put in are theirs, and they can export a project or download a database at any time — nothing here is locked in. We store and serve that work in order to run the platform, and we do not use it to train anything or publish it anywhere they did not publish it.
Published sites
Publishing puts a site on the public internet at its own address, which means anybody with the link can see it. Pupils are responsible for what they publish, and schools for supervising it. A published site can be unpublished at any time, by the pupil or by an administrator.
The assistant
Replies come from a large language model and will sometimes be wrong. Code it writes should be read before it is trusted, which is most of the point of the lesson. Each account has a weekly allowance, which exists to stop one runaway project spending a class’s share; an administrator can change it.
Availability
We try to keep it up and we do not promise that it will be. There is no uptime guarantee, maintenance happens, and a provider we depend on can have a bad day. Do not schedule an assessment in a way that a bad afternoon would ruin.
Liability
VibeStack is provided as it is. To the extent the law allows, we are not liable for lost work, lost data or lost time, and our total liability is limited to what the school paid us for the platform in the twelve months before the claim. Nothing here limits anything that cannot be limited by law.
Ending it
A school can stop using VibeStack whenever it likes and ask us to delete its accounts and their work. We can end access if these terms are broken, or if we stop running the platform — in which case we will give enough notice to get the work out.
Changes
If these terms change in a way that matters, the date at the top changes and we tell the schools using the platform.
Law
Singapore law governs these terms, and the Singapore courts have jurisdiction.