Keep your services.
Bring your releases together.

TapeNow is an invitation preview for building, verifying and publishing static websites, with a separate adapter for Cloudflare Worker modules.

Import from Vercel

1. Sign in with an invited email and create a TapeNow project.
2. Open Integrations → Vercel and enter your Vercel team URL slug (the part after vercel.com/). Authorize access to your selected project. TapeNow requests project and deployment metadata, not environment secrets.
3. Run the compatibility check. Vite and other static builds can be rebuilt. Server functions, SSR and vendor-specific services need separate adaptation.
4. Authorize the matching repository through the GitHub App. Review and install .github/workflows/tapenow-build.yml. Builds run on your own GitHub Actions quota, against the source deployment's exact commit.
5. Import the successful artifact, verify its source and files, then create a password-protected preview or explicitly confirm a public preview. Imports alone do not publish files. Your original Vercel website remains online. Domains, secrets and blockchain transactions are separate, explicit operations.

Other connections

Cloudflare provides Pages previews and production mirrors, plus explicitly requested Worker deployments. Supabase connects your existing project using its public client configuration. Supabase grants require Organizations, Projects and Secrets read access; TapeNow filters API keys and retains only publishable/anon keys, not service role keys.

Private previews and retention

Private preview passwords protect the page and its assets on a separate hostname for 1–168 hours. Regenerate or revoke access in the release details. A release that may already have been published cannot be made private again, and copies downloaded by authorized visitors cannot be recalled. Retention defaults to 30 days with automatic cleanup disabled; protected versions stay available. Trash can be restored for seven days before cloud cleanup removes the archived files. Chain records, external Pages copies and customer databases are not deleted.

Database environments and email

Bind separate Supabase projects for Preview and Production in Storage. A reachable Auth API is not proof of email delivery. Configure Custom SMTP in your Supabase dashboard and include {{ .Token }} in the Magic Link template, then send a test to your own signed-in email and verify the received code. TapeNow does not store customer SMTP credentials or execute SQL automatically.

Diagnostics

Project diagnostics count 30 days of requests, HTTP 4xx/5xx errors and file response bytes at TapeNow private and R2 public version origins only. They exclude external Pages, native chain gateways, browser JavaScript errors and provider billing. The TapeKit BSC/X Layer adapter checks files through two RPC providers without signing a transaction.

Project collaboration and existing databases

Owners can add invited accounts as Publishers or Viewers in project settings. Publishers can prepare releases; credentials, domains and members remain owner-managed. Storage checks preview/production PostgreSQL TLS and read-only sessions separately, or associates an existing business API. It does not create tables or generate APIs.

Three chains and ecosystem services

Choose BSC, X Layer or Base in project settings, with separate networks, currencies and budgets. The ecosystem page links One-Click Container, TapeOutScan/TapeWeb, HashPort and tapeout.work. HashPort serves BSC; the independent TapeNow Gateway supports ordinary HTTPS and customer subdomains across all three chains. Review and confirm CF DNS changes; chain verification and HTTPS access remain separate checks. See the Gateway guide.

Network gas and upstream activation are not TapeNow platform fees. Base currently charges 0.0012 ETH per 30 days directly to the upstream binding contract. BSC currently waives this service fee, but gas remains payable. Prices were checked on 28 September 2026; review a fresh quote before paying. See Fees explained.

Accounts and revocation

Provider tokens stay encrypted on the server. Removing a project binding does not delete your cloud resources. Revoke the account grant in TapeNow or the provider dashboard to end API access. Published websites and their public client keys remain public.

Questions or problems: sign in and send feedback from the workbench.

Privacy · Terms