What xTerminal is

xTerminal is the place you run a custom website. Whoever builds the site connects it. You run content, leads, and Requests from one dashboard. A developer keeps the code. A worker can build a change. A person reviews it before it is live.

The product direction is simple: we are the state intelligence operates on. The dashboard is that state. It is not a prompt box that emits a new site.

Not a website builder

xTerminal does not build or include a site. Signing up does not generate pages, a theme, or a storefront. Other tools hand the owner a generated site and a steering wheel. xTerminal keeps a developer between the owner and the code, and gives the owner a control panel for everything after connect.

• No generated site at signup.
• No claim that the dashboard is the website.
• The live site stays a real project the developer connects.

State, custody, and ops

Three jobs sit in the dashboard. Code, GitHub, and hosting stay in the developer lane.

State

Who is on the site, what they can change, which Request is open, and what already shipped. People and agents should be looking at the same board. That is why status, delivery, and membership live here instead of in a chat log.

Custody

The owner holds the site in the dashboard. The developer holds the repo and the host. Owners do not get a GitHub login as part of running the site. If you need a change that is not in Edit, you file a Request.

Ops

Everyday copy you edit yourself: a blog post, a team member, a form lead. Anything else you type as a Request. A worker can build it. A person reviews the preview. Then someone who is allowed to asks to Ship to live.

What you see in the dashboard

• A home with the site you are running, and a way to switch if you have more than one.
• Content you turned on: blog, team, and other types.
• Inbox for form leads. Pipeline when that tool is on.
• Requests, when the site is entitled and the switch is on.
• Settings for Team, billing, and (for admin or developer) worker connection.

Who it is for

• Owners who want one dashboard for the site, not a pile of tools.
• Admins the owner invites to help run content, Team, and billing.
• Developers who connect a custom site and review the work.
• Workers and agents that act on a Request, in a lane, with a person in the loop.

What this is not

• Not a host you buy inside the dashboard.
• Not a GitHub product. The owner never needs the repo to run the site.
• Not an app store of connectors. A few pipes are live. The rest is Coming soon on the Integrations pages.