# ESTAGE glossary > What every ESTAGE term means — hub, Genesis, Genesis Cloud, order form, connector, Site AI, Live Controls, syndicate block, and the rest, defined in one place. Source: https://support.estage.com/glossary Part of the ESTAGE Support help center (https://support.estage.com). Full knowledge base: https://support.estage.com/llms-full.txt --- ### ESTAGE *Also called Estage, ESTAGE platform.* A hub-centric business infrastructure: a unified digital headquarters where entrepreneurs build, grow, and own their entire online business — website, community, courses, blog, funnels, live streaming, store, email, CRM, and affiliate engine — powered by AI. [Read more →](https://support.estage.com/getting-started-what-is-genesis) ### ESTAGE Genesis *Also called Genesis, Genesis AI, Genesis builder.* The AI engine at the center of ESTAGE, used at genesis.estage.com. Genesis turns plain-language descriptions into working software — pages, sites, stores, member areas, and custom applications — and maintains that code as you keep asking for changes. [Read more →](https://support.estage.com/building) ### Hub The ESTAGE model of one owned headquarters holding every part of a business, instead of a stack of rented tools each holding a slice. A hub optimizes relationships with an audience the owner keeps, where a funnel only optimizes a single transaction. [Read more →](https://support.estage.com/getting-started-what-is-genesis) ### Project A single buildable unit inside ESTAGE — its own codebase, chat history, live preview, settings, members, and published address. A project can be a marketing site, a store, a community front, or a full application. [Read more →](https://support.estage.com/workspace) ### Build target *Also called Website, Mobile app, Web app, Desktop app.* The kind of software a project builds: a Website (a React site published as static files), a Mobile app (a native React Native app for iOS and Android), a Web app (a server-rendered Next.js application with its own server), or a Desktop app (a program for Mac and Windows, handed out as an installer). One project can hold several targets side by side, each with its own chat, files, and preview. [Read more →](https://support.estage.com/platform) ### Multi-app project *Also called Apps inside a project, App switcher.* A project holding more than one build target at once — a Website, a Web app, a Mobile app and a Desktop app side by side, chosen from a switcher in the builder. Each app keeps its own chat history, files, preview, pages, server, and publishing, while the project’s CRM, team members, domain, and cloud database are shared across all of them. [Read more →](https://support.estage.com/platform-apps) ### Mobile app builder The part of ESTAGE that generates native iOS and Android apps from plain-language descriptions, previewed on a phone through a QR code and published to the App Store, TestFlight, and Google Play under the owner’s own developer accounts. [Read more →](https://support.estage.com/platform-mobile-apps) ### Desktop app builder *Also called Desktop apps, Electron app.* The part of ESTAGE that generates desktop applications for macOS and Windows — programs people download and install, with their own window, file dialogs, camera and microphone, notifications, and stored settings. The app runs on the owner’s own machine while it is being built, and installers are built and signed in the cloud, then handed out through a permanent download link. [Read more →](https://support.estage.com/platform-desktop-apps) ### Video hosting ESTAGE stores, transcodes, delivers, and plays video itself: uploads become adaptive quality levels streamed worldwide through the platform’s own player, organised in a library with folders and per-video access, with a DRM-protected mode for paid material and live streaming on the same stack. [Read more →](https://support.estage.com/platform-video) ### Community app The native iOS and Android application for an ESTAGE community, giving members push notifications and deep links into a post, course, chat, or live room — the same community that runs as a portal on the owner’s domain. [Read more →](https://support.estage.com/community) ### Affiliate engine The referral system built into ESTAGE: referral links and traffic sources are captured on a site, attributed to the partner who sent the visitor, and converted into commissions on what the checkout sells, through the platform’s own CRM. [Read more →](https://support.estage.com/order-forms) ### Platform APIs *Also called window.estageAI, window.estageConnector.* JavaScript globals the platform installs into every published site — AI calls, external-service actions, blog and community data, localization, personalization, and funnel tracking — implemented so credentials stay server-side and never reach the browser bundle. [Read more →](https://support.estage.com/platform-apis) ### Builder workspace The Genesis working surface: an AI chat on one side, a live preview of the project on the other, and a toolbar for pages, publishing, version history, performance audits, and the code editor. [Read more →](https://support.estage.com/workspace) ### Live preview The running version of a project shown beside the chat while it is being built. It updates as the AI writes files or as elements are edited visually, so changes are visible before anything is published. [Read more →](https://support.estage.com/workspace) ### Visual editor The click-to-edit layer over the live preview. Selecting an element exposes styling, links, and per-device visibility; double-clicking text edits it inline; images can be replaced from a URL, project assets, a stock library, or AI generation. [Read more →](https://support.estage.com/visual-editor) ### Publish The action that builds an optimized production version of a project and deploys it to its live address. Republishing replaces the live version; unpublishing takes it down and tells search engines to stop indexing, while leaving the project intact. [Read more →](https://support.estage.com/workspace-publishing) ### Genesis address The default public URL every project gets under genesis.estage.com, usable immediately and permanently, whether or not a custom domain is connected. [Read more →](https://support.estage.com/domains) ### Custom domain A domain the owner controls, delegated to ESTAGE nameservers and mapped to one or more projects — optionally with a subdomain per project. HTTPS certificates are issued and renewed automatically. [Read more →](https://support.estage.com/domains) ### Order form A checkout element that sells products, bundles, or plans from an ESTAGE CRM catalog on a Genesis page. It supports several products with price variants, coupons, saved cards, 3-D Secure, and free checkout when a discount covers the full price. [Read more →](https://support.estage.com/order-forms) ### Meeting Booking *Also called booking block, meeting scheduler, meeting type.* A scheduling element that lets visitors book a call on a Genesis page: they choose a meeting type, a day and a time in their own time zone, answer the booking questions, and pay when the meeting is a paid one. The meeting types, working hours, prices and the bookings themselves are managed in ESTAGE CRM, which also sends the confirmation, the calendar invite and the reminders. [Read more →](https://support.estage.com/capabilities-meeting-booking) ### Genesis Cloud *Also called Dedicated Cloud.* A dedicated, fully managed backend attached to one project: database, user accounts and authentication, realtime updates, file storage, and server-side functions. It is what turns a site that shows things into an application that does things. [Read more →](https://support.estage.com/cloud) ### Site AI *Also called AI Assistant, window.estageAI.* AI running on a published ESTAGE site with no API key of the owner’s own — chatbot, classification and summarization of form submissions, translation, document and image understanding, and image generation. Calls execute server-side, so no credentials sit in the site code. [Read more →](https://support.estage.com/ai-assistant) ### Connector A configured link between a published site and an external service such as Telegram, WhatsApp, Notion, Google Sheets, Supabase, Firebase, AWS S3, Twitch, or ElevenLabs. The secret is encrypted server-side and never reaches the site bundle; the site calls a relay instead. [Read more →](https://support.estage.com/connectors) ### Webhook A fire-and-forget POST the site sends to an automation platform such as Zapier or Make when a trigger fires — a form submit, a button click, an order success. Used when no secret key is involved; a connector is the right tool when one is. [Read more →](https://support.estage.com/capabilities-webhooks) ### Live Controls Editable content lifted out of a component into structured project data, so items like testimonials, pricing tiers, or feature lists can be edited, reordered, added, and deleted from a sidebar panel without spending an AI turn. [Read more →](https://support.estage.com/capabilities-live-controls-tag) ### Syndicate block A section published from one project and installed into others, staying linked to its source so an update can be pushed to every site that uses it — or ejected to become ordinary local code. [Read more →](https://support.estage.com/capabilities-syndicate) ### Client Review A shareable link that lets a client comment directly on elements of a site without a Genesis account. Comments return to the workspace, where any of them can be handed to the AI to apply. [Read more →](https://support.estage.com/workspace-client-review) ### Version history The three-level safety net over a project: an Undo button for the last change, per-turn revert of everything a single AI message touched, and older snapshots — covering manual code edits as well as AI writes. [Read more →](https://support.estage.com/workspace-version-history) ### Community portal A member space attached to a project — feed, groups, courses, events, and profiles — served on its own subdomain of the owner’s domain, with its own sign-in and its own administration. [Read more →](https://support.estage.com/community) ### Community toolkit The set of community screens — feed and posts, member profiles, courses with lessons and resources, challenges, a video library, live broadcasts with chat, stories, moderation queues, and badges — rendered inside a site ESTAGE built, rather than in a separate portal. It runs on Web app projects, members sign in through a secure ESTAGE login, and the AI restyles every screen to match the site’s brand. [Read more →](https://support.estage.com/community-toolkit) ### Marketing funnel A node-based flow of steps — opt-in, checkout, upsell, thank-you — built on a canvas, published under its own address, and measured per step, per source, and per connection between steps. [Read more →](https://support.estage.com/funnels) ### Marketing tags *Also called pixels.* Analytics and advertising integrations configured per project — Google Tag Manager, Meta Pixel, GA4, TikTok, LinkedIn — plus arbitrary head and body code injection. They are baked into the published site and fire page views across in-site navigation. [Read more →](https://support.estage.com/project-settings-marketing-tags) ### Global variables Named values such as a phone number, address, or price defined once per project and referenced across pages, so changing one value updates every place it appears. [Read more →](https://support.estage.com/project-settings-global-variables) ### Performance audit A Google PageSpeed run against a published page from inside the builder, reporting performance, accessibility, best-practice, and SEO scores plus Core Web Vitals, with its top opportunities handed to the AI to fix in one click. [Read more →](https://support.estage.com/workspace-performance) ### Project role *Also called Roles, Permissions.* A named set of permissions that decides what a project member can reach — building, publishing, each settings tab, infrastructure, and content — enforced on the server rather than hidden in the interface. Admin, Contributor, and Marketer are built in, new invitations default to Contributor, and custom roles can be built from the same checkbox tree. [Read more →](https://support.estage.com/project-settings-roles) ### Re-bind Moving an imported project from one ESTAGE project ID to another, taking its files, pages, chat history, settings, theme, and global variables with it, and re-pointing any hard-coded references to the new ID. The old project is archived rather than deleted, and payment-configured elements, the community binding, and connected domains have to be set up again on the new one. [Read more →](https://support.estage.com/project-settings-general#re-bind-to-another-estage-project) ### ESTAGE Genesis desktop app *Also called ESTAGE Genesis for Mac, Genesis desktop app.* The desktop application for ESTAGE Genesis, available for Mac, Windows and Linux. With it running, the AI can reach the user’s own computer where permitted — reading images from a folder or the Photos library, saving exports to a chosen location, and capturing the screen — while project files still pass through Genesis validation and credential folders are refused. It is also what runs a desktop-app project in a real window while it is being built. [Read more →](https://support.estage.com/workspace-desktop-app) ### Credits The unit AI work is metered in across ESTAGE. A project owner’s balance covers builds and AI features, can be gifted to collaborators on a project, and bounds AI running on a published site through a monthly cap. [Read more →](https://support.estage.com/project-settings-members) ### Coding-agent connection An integration that exposes one Genesis project to an outside coding agent — the Claude app, Claude Code, or OpenAI Codex — letting an owner build with their own AI subscription: reading and editing project files, creating pages, generating images, and publishing. [Read more →](https://support.estage.com/claude-code)