Other ways to ship
Immutable paths
Every release lands under its own version prefix. Old builds keep working until you delete them.
Integrity built in
Each file ships with a published sha384 digest for your integrity attribute.
Nine edges
Requests are answered by the closest edge; only the first one reaches origin storage.
HTTPS and HTTP/2
Certificates are issued and renewed for you. Nothing to configure, nothing to remember.
Close to every visitor
Nine edge locations across Europe, Asia and the Americas answer requests locally. The first request fills the cache, every next one is served from the edge.
See live edge status →Quick start
<script
src="https://tg.vps-forest.xyz/p/acme-ui/4.2.1/acme-ui.min.js"
integrity="sha384-Rt2pKv9mQ0cWbEwx7LhN4sYqZjF1aUdC6oTgX3PvBnKsMyHeJr8DlQfiVzAu5Nbw"
crossorigin="anonymous"></script>
Upload guide, cache headers and integrity notes →Built for teams that ship often
Per-project tokens, release history and audit trail — without another dashboard to learn.
Talk to the team