hangar c · assembly · telep forge
telep forge.
a website editor and publishing studio. write your pages, pick a visual style, preview them, then publish to a private github repository and a vercel project that both belong to you.
Preview status. The studio is built to live at studio.telep.tools. Its automated and browser checks pass with mocked provider responses, but full live customer onboarding and publishing have not been verified yet, so Forge is not generally available. This page describes what is implemented today, not a roadmap.
what it does
a structured content editor with a publishing pipeline behind it. not a code ide.
Editing
- Create content websites and choose a visual style.
- Add and remove pages. Edit each page's heading, introduction, and sections.
- Reorder sections. Add images by HTTPS URL with alternative text.
- Preview saved content at desktop and mobile widths.
- Save private drafts and undo the previous saved edit.
- Optionally edit content through AI chat.
Publishing
- Connect your own GitHub and Vercel accounts by approving their authorization screens. No tokens to paste.
- Create a private GitHub repository for the website.
- Create a Vercel project and deploy the website into your Vercel account or team.
- See deployment status, with recovery and retry controls when something fails.
- Detect conflicting content changes between GitHub and your saved draft, and let you choose which to keep.
- Preserve unrelated repository files and custom renderer code across publishes.
who owns what
forge is the editor. everything it produces lands in accounts you control.
| thing | owner |
|---|---|
| The Forge GitHub App and Vercel integration registrations | Telep IO |
| Your GitHub and Vercel accounts, and the authorizations you grant | You |
| The generated repository and its contents | You |
| The Vercel project, its deployments, and any hosting usage or charges | You, under your Vercel account or team and plan |
| Your domain name | You, registered through your own registrar |
| The content, text, and images you publish | You. You must hold the rights to publish them. |
Published pages and the images they reference are public, even when the source repository is private. Generated websites are ordinary static sites and do not need a Telep runtime to keep running.
The Forge codebase is released under the MIT license. That license covers Forge's own code. It does not license your content under MIT or change who owns it.
current limitations
what is not implemented today. none of this is promised for a specific date.
- Repository creation works on personal GitHub accounts only, not organization-owned repositories.
- Forge is a structured content editor, not an arbitrary-code IDE.
- Image uploads, document ingestion, website crawling, and arbitrary layout or code generation are not implemented. Images are linked by HTTPS URL.
- Generated sites have no built-in database, visitor login, or contact-form backend.
- Custom renderer code in your repository is preserved but not executed inside Forge's preview, so the preview may differ from the deployed site.
- The Vercel connection must start from Forge's Connect Vercel button. Onboarding that starts from the Vercel marketplace is not supported yet.
read more
- docsgetting started, the publishing flow, custom domains, and what happens when you save versus deploy.
- supportfixes for github installation, vercel repository access, wrong-team errors, failed builds, and content conflicts.
- termsplain-language terms for the hosted service: scope, your content, acceptable use, third-party services.
- privacyexactly what forge stores, where your content is sent, cookies, and how to reach us.