quickish_
quickish_
Features
Start with a folder of HTML and a live URL. When you want more, a backend, real data, server code, your own domain, it's already there. No build step, no servers, nothing to wire up.
Instant hosting
Drop a file, a whole folder, or a zip, or run one command, and your page, site, or deck is online in seconds. Links between files just work, relative paths and all.
$ npm i -g quickish $ quickish # publish this folder ✓ live · you.quickish.site
Publish with AI
AI makes good-looking HTML, and it usually has nowhere to live. Connect Quickish once, then say “publish this to Quickish” and your page goes live, assets and all. No blank page either, remix a ready-made app and have any agent refine it.
Data & backend
Add one script tag and your page gets quick.db (a document store), file uploads, the signed-in visitor, live updates, and casting to a screen, with no keys to manage.
<script src="/quick.js"></script> const tasks = quick.db.collection("tasks"); await tasks.create({ title: "Ship it" }); const all = await tasks.list(); // done.
Functions
Drop a file in a functions/ folder and it becomes a server-side endpoint, so it can hold a secret API key, tally a vote nobody can stuff, or validate input before it touches your data.
quick.fn()export default async function (req, { env, db }) { // env.STRIPE_SECRET stays on the server const order = await db.collection("orders") .create({ items: req.body.items }); return { ok: true, id: order.id }; }
quick.sql
When your data grows relations, a leaderboard, a kanban, anything with joins, reach for quick.sql. It's managed Postgres behind one tagged-template call. No connection string, no provisioning.
sql/ folder; migrations run once at deployconst top = await quick.sql` select name, sum(points) as pts from scores group by name order by pts desc limit 10`;
Sharing & permissions
Every page can be private, shared with named people, company-wide, or fully public, and Quickish picks safe defaults so a public page is never a free-for-all.
$ quickish --private # only you $ quickish --invites a@co.com # named people $ quickish --workspace # your company $ quickish --public # anyone
Custom domains
Point your own host at a page and serve it at docs.acme.com instead of a Quickish URL, with an HTTPS certificate issued automatically. Your backend keeps working, untouched.
quick.db, quick.fn, quick.sql, and realtime all keep working$ quickish domains add docs.acme.com --path docs # add the two DNS records it prints, then: $ quickish domains verify docs.acme.com ✓ live · https://docs.acme.com
Localish New
Run quickish --localish and your running dev server gets a stable, private, sign-in-gated Quickish URL, hot reload and all. No deploy, no third-party tunnel, nothing exposed to the public web.
localhost to a real, sign-in-gated URL$ quickish --localish # tunnel your dev server ● tunneling localhost:5173 ✓ live · you.quickish.site/_localish/app/
Develop locally New
quickish dev emulates all of Quickish offline, quick.db, quick.sql, functions, file uploads, identity, and realtime, so you (or an AI agent in a sandbox) can build and test a real stateful app with no account and no network, then publish it unchanged.
$ quickish dev # backend, offline ● quick.db · quick.sql · quick.fn · files ✓ localhost:4321 · no account, no network $ quickish # ship it, unchanged
Free for one live page per person. Drop a file, run a command, or just ask your AI.