juudd

Terms of Service

juudd — Just Upload. Done. Deployed.

These terms are between you and MATTREK TECHNOLOGY CO., LTD. (บริษัท แม็ทเทรค เทคโนโลยี จำกัด). Using the service means you accept them. Effective September 2, 2026.

What the service is

juudd is an MCP server. You connect it to the AI assistant you already use, and its tools deploy a website with static files, plain-JavaScript server functions, and a Postgres database, served on your own URL. You sign in with OAuth; there are no API keys and no second account to create anywhere else. The tools' own descriptions are the authoritative reference for what each one does, and every tool declares whether it reads, writes, or does something irreversible.

Your account

Your account is the identity your sign-in provider vouches for. Every site has exactly one owner account, and every tool refuses a site the caller does not own. You are responsible for what happens through your session, including what your AI assistant does with the tools while acting for you.

Site ids and domains

Site ids are first come, first served, in one global namespace, and an id becomes a public hostname. Claiming one gives you the use of it, not a trademark. You can point a domain you already own at a site; we do not register domains for you. DNS at your registrar is yours to manage, and if you release a domain here it immediately becomes claimable by anyone, including another account, so remove your DNS record when you leave.

Your content

What you deploy stays yours. You give us the right to store it and serve it to anyone who requests your site, which is the entire point of deploying it. Treat everything you deploy as public: static files are served to any visitor, and you must keep credentials and secrets out of files and functions alike. The tools warn your assistant about this; the warning is part of the product.

You must not deploy anything unlawful, or content that is malware, phishing, or an impersonation, and you must hold the rights to what you deploy. We may stop serving a site that breaks this, and because nothing is ever deleted, "stop serving" is what enforcement looks like here.

Databases

create_database makes a Postgres database for a site, in our account at our provider. The owner connection string is shown to you in the panel, for a person at a terminal; it is not returned to your assistant. A table must carry a row-level security policy before a site can be deployed against it, and the deploy tool refuses otherwise. transfer_database moves the database into your own account, after which we lose all access to it, permanently: we cannot read it, back it up, or get it back, and repairing its credentials becomes yours to do with set_database_url. There is no deadline on the exit and a fresh transfer link can be minted at any age.

Five things the service will not do

Stated up front because they are the five most likely to end your afternoon:

  1. It will not build a framework project. No install step, no bundler. Server code is plain JavaScript, and the only npm import allowed is the Neon driver.
  2. It will not show server logs. Nothing captures what a function printed. What a request returns is what you debug from.
  3. It will not delete anything. Every deployed version stays, which is what makes a rollback a publish and not a restore. A site can be replaced, never wiped.
  4. It will not serve an apex domain everywhere. A bare example.com works only where your DNS provider flattens CNAMEs or offers ALIAS records; otherwise use www and redirect the apex yourself.
  5. It will not take a domain behind another CDN. Ownership is proven through DNS, and another CDN in front hides exactly what has to be read.

Your end users

If your deployed site collects personal data from its visitors, you are the controller of that data and we are a processor. We never use it for our own benefit. Complying with the privacy law that applies to your site, including what you tell your visitors, is your responsibility. Our privacy policy lists the sub-processors involved.

Fees

The free tier is permanent, not a trial: two sites of static files, served at their platform address, with no database and no custom domain. Deploying server functions on a free account is not refused; the code is stored whole, and a request to a function route answers 402 until the account is on the paid tier. The paid tier is $12 per month for up to ten sites, a database, and your own domain, with $12 of usage included and usage beyond that metered. Neither tier counts requests: traffic your site did not cause is the platform's to absorb. Every new account gets sixty days of the paid tier, counted from that account's own arrival, and a card is taken at the start. Day 61 is a downgrade, not a cliff: if you stop paying, your site keeps serving as static, your functions remain stored and answer 402, and your database keeps working for seven days, is then stopped, and is never deleted. You can take it at any time with transfer_database, which has no deadline.

None of this is billed yet. There is no way to pay today, and nothing is charged until billing exists. When billing goes live, payment will be handled by Stripe and these terms will be updated first.

What we promise, and where the promise ends

We promise the durability described above: every version stored, ownership enforced, the exit door always open. Beyond that the service is provided as is. Deployed sites are served by an edge network we do not operate, DNS propagation is governed by TTLs nobody here controls, and certificate timing for your own domain is something we have not measured and therefore do not promise. We are not liable for indirect or consequential loss, for what your site does to its visitors, or for a database after you have transferred it. Where liability cannot be excluded, it is capped at the amount you paid us in the twelve months before the event giving rise to the claim, or $12 if that is greater.

Suspension and ending

We may stop serving a site, or suspend an account, for breach of these terms. If you leave: take your code with read_site, take your database with transfer_database, and release your domains. Your stored versions remain stored, because nothing is deleted; they simply stop being served anywhere new.

Changes and law

We may change these terms; the change will say what changed, and material changes will be announced before they apply. These terms are governed by the law of Thailand, and disputes go to the courts of Thailand.

Questions: alongkot.sa@mattrek.co. A person reads that address.