Loops HouseQuay

NEAR HACKATHON
Team
1 member- SAOwner
Sailesh Sivakumar
Overview
A NEAR app's contract lives on chain, but its website usually sits on a web host the team rents and controls. Web4 lets a contract serve pages. Quay adds the deploy loop a host gives you, on one NEAR account.
quay deploy ./dist uploads a folder to the account's contract and seals it as a numbered release with its own preview URL. quay promote 3 points production at release 3 and quay rollback swaps it back, one transaction each. A publish-only function-call key can upload previews from CI or an agent, but it cannot move production: the contract refuses it on chain. A dashboard reads releases, storage and keys from the chain with no key, and promotes through a wallet. The bytes and the production pointer are contract state anyone can read; Cloudflare Workers, testnet.page or quay gateway on your own machine only serve them.
The same account can also hold a document store, members created with no NEAR whose writes a relayer pays for, Rust functions run on OutLayer, payments in NEAR or a token, and a cron job the contract keeps running. Harbour Board, the sample app, uses all of them on testnet.
How NEAR fits: the contract uses near-sdk 5.30. Storage staking pays for the bytes, about 1 NEAR per 100 KB, unlocked when a release is deleted. Function-call keys are the permission model, NEP-366 delegates carry members' writes, and NEP-413 messages sign people in.
Testnet only. Live: https://quay.ss251.workers.dev. sh scripts/judge.sh checks the live contracts and pages without a key.