Why TeleportHQ?

A developer? What TeleportHQ gives you, and what you keep in code

A developer? What TeleportHQ gives you, and what you keep in code

For a developer, TeleportHQ is a visual editor whose output is code you can take: a website downloads as React, Next.js, Vue, Nuxt, Angular or HTML, or goes straight to GitHub, generated by TeleportHQ's open-source generators. Inside a project you add your own HTML, CSS and JavaScript, connect REST APIs and databases, start workflows from webhooks and run your own JavaScript on the server. The limit is also plain: a web app (sign-in, a store, bookings, a blog, a help center, a newsletter) runs on TeleportHQ's servers and its code can't be exported. This guide says what you get, what you keep in code and what you will be asked to decide.

Who this is for

  • You can code and want to skip the scaffolding: pages, styling, forms, sign-in, a store, emails.
  • A client wants a site they can edit themselves afterwards, and you want to know what you get back if they leave.
  • You are checking what the "export your code" claim means before you start.

What you get on day one

  • Generated code, from open-source generators. The editor's output is produced by teleport-code-generators, an MIT-licensed project on GitHub with a generator per target: React, Next.js, Vue, Nuxt, Angular and HTML. On a paid plan (Pro or Premium), click Code at the top right of the editor, open Download, pick a format and click Download ZIP; the ZIP holds your pages, components, styles, images, fonts and the code from Project settings → Custom code. Export to GitHub creates or updates a repository with a classic personal access token that has the repo scope. A trial lets you view the code (10 views per workspace) but not download it. See How to download your site as code (React, Next.js, Vue, HTML and more) and How to export your project to GitHub.
  • Your own code in three places. A Code Embed element holds HTML, CSS and JavaScript at one spot on a page. Project settings → Data & code → Custom code puts script, style, meta or link tags in the head or body of every page of the published site (they don't run on the editor canvas). The Advanced tab of the right panel takes any CSS property the Visual tab lacks, per element and per screen width. See How to add your own HTML or JavaScript with Code Embed, How to add code to every page (head and body) and How to write CSS directly (Advanced tab).
  • Data sources. A database, a spreadsheet, a headless CMS or a REST API (URL, method, headers, authorisation, with cached answers if you want), plus the built-in TeleportHQ database with up to 200,000 records per table on a paid plan. A list repeats one design per row, and a details page gives each row an address such as /products/blue-shirt. Connecting a data source keeps a website a website. See What are data sources, and which ones can I connect? and How to connect a REST API.
  • Workflows with your JavaScript. A workflow is one trigger and a chain of steps. Triggers include a click, a form submission, Scheduled (Cron) (for example daily at 9 AM in a time zone you pick) and Webhook Received, which gives you an endpoint URL to paste into Stripe, Zapier or Typeform. Steps save, update or delete records, send email or SMS, call other apps, and Custom JavaScript runs your own function, in the browser or on the server, with the earlier steps' results in params. Each step can be tested on its own. See What are workflows?, How to start a workflow from a webhook, How to run a workflow on a schedule and Workflow triggers and steps reference.
  • Your own AI keys. Under Project settings → Credentials → AI Providers, an OpenAI, Anthropic, Google, Cohere, Mistral AI, Together AI or Perplexity key runs the AI steps of your workflows, and the visitor chatbot runs on your OpenAI key; the provider bills you directly. See How to use your own AI provider keys in your web app.
  • Staging, deployments and domains. Publish to Staging serves a private address; Make it live promotes that build; Deployments lists every publish with a way to put an earlier one back; a custom domain is two DNS records. See How to test changes on a staging site before going live and How to see and manage your deployments.

What can't be exported

  • A web app. Sign-in, workflows with server steps, a store, bookings, a blog, a help center, a newsletter, an admin panel and the chatbot run on TeleportHQ's servers. A web app has no Code button and no Download tab. To get the download back, Switch to Presentation Website in Project settings → General turns those plugins off and deletes the workflows, global states and the project's own database, after a backup when your plan has one; a store the AI built can't be switched back. See How to turn a website into a web app.
  • Some websites export to fewer formats. A website connected to a data source downloads as Next only; a website in several languages as Next or HTML (an HTML download holds one language).
  • Browser widgets ride only in Next. Calendar, Countdown, Kanban Board, QR Code, Barcode, Signature Pad, Color Picker, Emoji Picker, File Upload Field, Drag Area, Sortable List, Cookie Consent and the language switcher work in the Next download and come out empty or without their behaviour in the others. Charts work in Next and React. Motion elements, scroll scenes and page transitions play in Next and HTML; the other formats get the same content without the animation. The Download tab names the ones your project uses. See Can I download my site's code?.
  • Popups need the published site. The HTML download doesn't open them.
  • The project file is not a site. The last card in Download, Download File, saves one .json file that describes the project for the open-source generators. It isn't a site you can run or upload to a host.

What happens in the first week

  • Publish, then read the checks. After each publish to Production, the Publish window lists what visitors would run into (broken links, empty pages, images without alt text) and a Check page loading speed button shows which pages are slow on phones. The Issues window in the editor header finds missing settings and links that lead nowhere before you publish. See What should I check after publishing my site?.
  • An audit you didn't schedule. Every week TeleportHQ audits up to 30 pages for Performance, SEO, Accessibility and Best practices and alerts you when a score falls 10 points or more; it also tries every internal link on up to 60 pages and checks every 15 minutes that the homepage answers. See How to keep an eye on your site every week (SEO Monitoring).
  • Errors reach you as cards. The coach's card "Errors hit 12% of visits on /checkout" quotes the first 80 characters of the script error; "Errors spiked yesterday" is Critical and emailed at once. See How to see what to do next for your site (Growth → Today).
  • Funnels count tracked events. A funnel of 2 to 8 steps mixes page visits, clicks on an element and tracked events. See How to track steps to a sale or signup (Funnels).

What you will be asked to decide

  • Website or web app. The Enable Web App features? window opens the first time something needs a server. Say no (Keep as a Presentation Website) and the code stays exportable; say yes and the project is hosted by TeleportHQ until you switch it back, which removes those features. See What's the difference between a website and a web app?.
  • Which target. Next if you use a data source, several languages, widgets, charts or motion; HTML for a plain page; React, Vue, Nuxt or Angular when you need that stack and can live without the widgets.
  • TeleportHQ's database or yours. Bookings and the Newsletter keep their records in the TeleportHQ database only; a project whose features already use a database you connected can't switch them on. A store, a blog and sign-in can use either. See How to set up the built-in TeleportHQ database.
  • Where custom logic lives. A Custom JavaScript step on the server, or your own service called as a REST API or through a webhook. A backend of your own, in its own language and framework, runs elsewhere.
  • Workspace AI tokens or your own keys for the AI steps your workflows run.

Where to start

  1. Can I download my site's code?: the rules by plan, project type and role.
  2. How to download your site as code (React, Next.js, Vue, HTML and more)
  3. What are workflows?, then How to start a workflow from a webhook
  4. How to connect a REST API
  5. TeleportHQ compared with ChatGPT and Claude Code: when a coding assistant is the better route.
Share

Related Articles

Can I download my site's code?

Yes, on a paid TeleportHQ plan (Pro or Premium) you can download a website's code as HTML, React, Next.js, Vue, Nuxt or Angular, or export it to GitHub; a trial only lets you view the code (10 code views), and web apps can't be downloaded as code.

How to download your site as code (React, Next.js, Vue, HTML and more)

On a paid TeleportHQ plan (Pro or Premium), click Code at the top right of the editor, open the Download tab, pick a format such as HTML, React or Next and click Download ZIP to save your website's source code; a trial can't download code and web apps can't be downloaded.

How to export your project to GitHub

On a paid TeleportHQ plan, open Code → Download, pick a format, click Export to GitHub, paste a classic GitHub personal access token with the repo scope and click Export to GitHub again; TeleportHQ creates or updates a repository with your website's code.

What are workflows?

A workflow in TeleportHQ is a visual recipe that makes your web app do something, one trigger (like a button click or a form submission) followed by steps (like saving to a database, sending an email or opening a page), built without writing code; a workflow whose steps need the server makes a website a web app, while one that only changes the visitor's page doesn't.

How to start a workflow from a webhook

In TeleportHQ, replace a workflow's trigger with Webhook Received, copy its endpoint URL, publish your site, and paste the URL into the other service (for example Stripe, Zapier or Typeform) so its requests start the workflow on your server.

How to connect a REST API

In TeleportHQ, you connect a REST API from Data Sources → Add Data Source → REST API by entering the API URL, choosing the method, adding any headers or authorization, clicking Fetch data from API and then Save Data Source; you can also cache the API's answers, or ask the AI Assistant to connect a public API.