Skip to main content
A bundle is a folder of files put online as one unit. Where an artifact is one file, a bundle is a whole folder, and its main use is a live website.

Why use bundles

  • A multi-page site works as a site. Links between the pages work, images and styles load, and scripts run.
  • You do not need a hosting account. Your agent deploys the folder and hands you a link.
  • A bad release is not a problem. Each deploy is a version, and you can go back to an earlier one.
Example. A consultant’s agent builds a five-page training course with images and a quiz. It deploys the folder as a bundle. The consultant sends the link to the client, and the course opens in the browser like any website.

Put a site online

Your agent deploys a folder and gets two links back:
  • The live site, which shows the pages as a website.
  • The bundle’s page, which lists the files and links to the live site and to a download of the whole folder.
The site opens on its home page file unless the agent names a different one.
Example. A dev team’s agent builds the documentation for a release and deploys the output folder. The team shares the live link in the release announcement.

Release a new version, or go back

Deploying again to the same bundle makes a new version at the same link. If the new version is wrong, the agent switches the bundle back to an earlier one.
Example. An online shop’s agent updates the holiday gift guide and breaks the layout. The owner says “go back to yesterday’s version”, and the old guide is live again.

Choose who can see it

Example. An agency deploys a campaign microsite by link while the client reviews it, and a public one on launch day.

What you see

The web app has no bundles page. You deploy and manage bundles through your agent.
  • The bundle’s page: the file list, a link to the live site and a download.
  • Trash: a deleted bundle shows on the Trash page, where you can restore it.

Ask your agent

  • “Deploy the site folder as a bundle and give me the live link.”
  • “Deploy the new build as a new version of the course site.”
  • “Roll the gift guide back to the previous version.”
  • “List my bundles.”

Good to know

  • A bundle is a static site: pages, styles, scripts and images. It runs no server code.
  • Live sites are served from their own address, apart from the Tokenrip web app. Fonts and scripts from other sites load as usual.
  • A bundle’s title, short name and visibility belong to the bundle. A new version does not change them.
  • Every version of a bundle counts toward your storage.
  • Deleting a bundle moves it to the trash for 30 days.

For agents and developers

Bundle rules

Deploying, the options, visibility and how agents read a bundle

CLI overview

Where the deploy and bundle commands sit