Give PitchStation a brochure or a short description, and AI drafts the whole site. You edit it, send it to your client for approval on a link, and publish it to your own server once they approve.
Open Website. The ✨ Create new tab walks you through four numbered steps: the draft, your brand assets, the content and the style.
Pick whichever source you have:
.txt/.md file) on the box, or click to browse. While it works you'll see “Reading … — extracting text, drafting content, pulling images…”. A long brochure can take a minute or two; keep the tab open. When it says “✓ Processed”, the forms below are filled in.From a PDF, PitchStation also pulls out the pictures. Under Image candidates from the PDF, click Use as logo, Use as hero or Material on any of them.
The draft lands in cards you can edit directly: Company, Brand (this site), Hero, About, Insights (monthly updates), FAQ and Contact. Read every card before you generate. AI drafts are a starting point, and only you know whether the phone number and the claims are right.
meta.industry); Industry key (for the style suggestion) picks the closest of the industries the style families are made for (meta.industry_key). The AI draft fills both when it can.hero.media.callouts). On a Friendly site, Shops on the map pins your shops on a map image (locations[].map_pin): it lists and numbers the shops the way the map does, the first eight with a name or an address. Select a callout or a shop, then click the picture; add shops in their own card first.meta.section_order in the JSON editor.bilibili.com/video/BV… or av…, and the player link), Tencent Video (v.qq.com/x/page/…, /x/cover/… or a link with ?vid=) and an https:// link to an .mp4 file. Short links such as b23.tv are never followed: paste the full page link. Nothing loads until a visitor presses Play. On a family site the video shows after About unless your section order places it; Tech Launch has no video section, so a video saved on it does not show. Families can also show a poster from your own images and a caption (video.poster, video.caption in the JSON editor).meta.icp, at most 40 characters, e.g. 沪ICP备00000000号): a classic template shows it on one line under the copyright row, with the 公网安备 record (meta.police_record) beside it; style families show both in their footers, linked to the filing sites.Every text box has a ✦ AI button. Choose Shorter, More formal, More vivid, → English or → 中文, or type your own instruction and click Rewrite. You see the suggestion next to your text and pick Use this or Discard. Nothing changes until you choose.
A site wears either a style family or a classic template.
tech), Industrial Spec (industrial), Editorial Lookbook (lookbook), Friendly Local (friendly), Grand Corporate (grand), Boardroom (boardroom), Maison Luxe (luxe) and Ink & Seal (inkseal). Their fonts are served from the site itself, never from Google.Click Preview my content in every style. Each card shows your client's own content in one style. Palette chips switch the palette; Desktop and Phone switch the view; tick two cards and Compare the two; On my phone makes a QR code for a phone preview. Cards also list the Photos you will need and warn when a style's showcase sections are still empty. After an AI draft the suggested style is marked Suggested (and selected, unless you already picked one or your account is partner-locked), and Also a fit marks up to two more, each with its own reason; when the content gives no hint, nothing is suggested. Use it as the accent copies a colour read from the logo into the Brand card. In 🗂 Manage / update, Change style opens the same gallery for a saved site.
The template select beside Generate website follows your choice (classic templates and style families in two groups). Moving a site to another kind of style keeps its content; the section order starts again from the new style's own, and pages whose sections the new style lacks are trimmed (the page says so).
The phone link from the QR code opens without signing in, for one hour: anyone who has it can see that preview. At most five stay open per person; a new one closes your oldest. The gallery's pictures are made on the server when the server has them switched on; otherwise the cards are live previews of the same pages.
On a partner-locked account the template select shows what will render and is disabled: a classic template renders as the partner template, and a style family keeps its design in the partner's colours, fonts and logo treatment. Manage uses the site owner's lock and brand, also when a co-manager opens the site.
Brand (this site) sets this site's Accent, Ink (text) and Paper (page ground) (picker or hex, with live contrast badges) and its Font pair for Latin headings and body (Montserrat, Inter, Playfair Display or Lora). On a style family it also offers Logo treatment (original colours, one colour in the ink, one light colour, or on a white chip) and, where the family uses them, Photo grade (Industrial Spec, Maison Luxe), Seal text of 1–8 characters (Ink & Seal) and Brand name on two lines (Tech Launch, Friendly Local, Grand Corporate: the name with one | where the second line starts, such as Harbour|Coffee; when it no longer spells the name, the style splits the name itself). Each field says where its value comes from: this site only, account default, the style's own or the partner lock (whose fields are disabled). From the logo reads an accent from the logo on the server; Reset to account default gives a field back to the account.
Only the fields you change are stored, in content.meta.brand (accent, ink, paper, font_pair, logo_treatment, seal_text, photo_grade, name_break); the rest follow the account's brand tokens, so a later account rebrand still reaches them. On a style family the brand colours also move the family's own accent shades with them (each family's pack decides which follow and how), text that would no longer read is lifted to its contrast, and a font pair maps to the family's self-hosted faces. Classic templates use the accent, ink and paper (ink and paper together) and the font pair.
Preview, beside Generate and Save, opens a pane with the page at 1280 pixels scaled to fit, or on a phone, and the render notes in words. It saves nothing: no revision, no quota, no change to a review. It renders what a save would: the template after a partner lock, the site owner's brand for a saved site, the self-hosted fonts. Where a page cannot load a video player (the editor's previews, a review link), the video box says it plays on the published site.
Generate, Save and Preview tell you what to check, in words on the page; integrations get the codes:
| Code | What it means |
|---|---|
CONTENT_CAP | A family shows only part of a list (field, shown of sent). The content is kept; shorten the list or pick a style that shows it all. |
BRAND_CONTRAST | Ink on paper reads below 4.5:1. |
BRAND_ACCENT_ADJUSTED | The accent is too light or dark for text on this page: text uses an adjusted shade; buttons keep the accent. |
BRAND_SCHEME | Your paper turns a light style dark (or a dark one light); the note names the style's palettes drawn for that ground, if it has any. |
BRAND_LOCKED | The partner lock pins this field; the partner's value is used. |
BRAND_NAME_BREAK | The two-line name no longer spells the brand name; the style splits it itself. |
BRAND_PAIR | A classic template takes ink and paper together; a lone one was not applied. |
BAD_BRAND | A brand value that cannot be used. On a style family, a field it reads is refused with 400 BAD_BRAND; elsewhere the note says it was left out. |
Generate and Save return the notes in warnings[]. Font problems come separately, in fontWarnings[] (FONT_MISSING, FONT_SUBSET_FAILED), only on a server that lets family sites fall back to system fonts; a production server refuses instead with 503 FONTS_UNAVAILABLE. Preview answers with the page, so its notes travel in headers: X-Render-Warnings (JSON: CONTENT_CAP, the brand codes and the content-field notes as {code, path}) and X-Font-Warnings. The two share one 1,536-byte budget, font notes first and at most 384 bytes, so they fit nginx's default 4 KB response-header buffer: a long list is cut, so read a save's warnings[] for the complete set.
Click Generate website. The Your website is ready panel shows the site with three actions:
sitemap.xml, robots.txt, llms.txt) to host anywhere yourself.Keep editing and click Regenerate this site as often as you like. It updates the same site, so any link you've already sent keeps working. Start a new site instead clears the editor for a different company. If you close the tab mid-draft, the page offers Continue that draft when you come back.
Under Review & publish, click Submit for review. Optional settings:
You get a link like https://pitchstation.ai/s/<slug>?k=… with Copy, Open and a QR code. Send it however you like. Your client opens the actual site with a bar on top saying “Review this website”, and clicks either Approve ✓ or Request changes with a note on what to change. A client without an account just types their name, so you know who decided.
For a saved site, tick Let the client choose the style before you submit. Option 1 is the site's current style; pick one or two more in the gallery that opens (another family, or the same family in another palette), then click Submit with 2 styles or 3 styles. Each style is rendered once, from the same content, into the exact pages the client will see.
The review bar then shows the styles as tabs, in the site's language. On a tab other than the current choice the client sees Choose this style and Request changes; choosing makes that style the version under review (it neither approves nor publishes), and the client can change their mind until they approve or ask for changes. Approve ✓ appears only on the style under review, so the approval binds to the bytes the client chose. When a reviewer email names a PitchStation account, only that person can choose; you cannot choose for them. You and your co-managers get one email and push notice per burst of choices, about 90 seconds after the first, naming the latest one, and your page shows which style was chosen.
Editing the site drops the offered styles (the review moves to revising): submit again to offer them again. If your partner lock changes after the link went out, the client is told the styles no longer render as sent; submit the review again.
The status pill on your page follows along: draft → in review → approved, or changes requested. Make the changes, regenerate and submit again. As long as you keep the same reviewer, the client keeps the same link.
PitchStation publishes to a server you control over SSH, and can set up nginx or Caddy and an HTTPS certificate for you. You set the server up once and reuse it for every site.
Under Deploy targets (your VPS), click + Add a deploy target and fill in the label, host or IP, SSH user and port, web root, web server (nginx + certbot, Caddy, or none), domain settings and an SSH private key. Click Save target, then Test. The key is stored encrypted and never shown again. If your administrator has already assigned you a server, it's listed as Assigned by admin and you can skip this step.
Under Site address, either type a short name (the site becomes name.<base domain>) or paste a full domain you own, such as www.client.com, then click Save address. Names are unique across PitchStation, so if one is taken, try another.
Agencies can claim a domain once for the whole account in the 🗂 Manage / update tab, under Account base domain: enter e.g. sites.youragency.com, click Claim, add the TXT record and the wildcard A record it shows you, then click Verify DNS. After that, every site can be client.sites.youragency.com.
Save your site address and intended server before review. For an external hostname, add the TXT ownership record shown after saving, then save again to verify it. Changing the address updates the canonical URLs and requires a new review. The publish check refuses to deploy approved content under a different address.
Under Publish live, click Deploy to VPS to do it in one go. To check first, click Preview deploy plan, read what will happen, then Publish live. The site is then at https://<your address>/.
Publish history lists every release; Roll back last release restores the previous one. Once live, Live traffic — published site shows 30 days of visits, top pages and where visitors came from. It uses no cookies and honours Do Not Track.
https:// and the host) of each linked .mp4 file, at most eight origins per site. Serve an .mp4 over https:// from that host itself: a file that redirects to another host is blocked. The Bilibili and Tencent Video players have not yet been tried on a published site; play one on a test site before you promise it to a client. Classic templates keep their policy and play YouTube and Vimeo.Switch to 🗂 Manage / update and pick the site under Choose a website.
Open pitchstation.ai/m/website/ (or tap Open app on the banner when you visit Website on a phone) and add it to your home screen. In the app you can:
Adding servers, the full section editor, the Brand card and the classic page layouts are on the desktop page, and so is moving a style-family site back to a classic template. Quick edits use the site owner’s partner lock; a new draft uses your account’s. The phone preview shows the home page only.
Once your assistant is connected (Connect your AI), it can run the whole journey with the MCP tools pitchstation_website_generate, …_update, …_status, …_submit_review and …_publish. Ask in plain words, for example “Make a website for YOUR_COMPANY from this brochure text, use the Friendly Local style, and send it to APPROVER_EMAIL for approval.” The tools set a style through content.meta.template and meta.palette, and the review tool submits the saved style only: style suggestions, the gallery and offering the client two or three styles go through the REST routes below.
For a long text brief, use POST /api/website/generate?async=1 and poll GET /api/website/extract/jobs/<jobId>. Keep a stable external_ref when retrying. A pending response means the work is still running. With a full content model, set the template on content.meta.template; meta_overrides applies to the brief path.
Without MCP, use an API token with the Website integration scopes (websites:read, websites:write, websites:publish):
# 1. draft content from text (or send a PDF as multipart field "pdf")
curl -X POST https://pitchstation.ai/api/website/extract \
-H "Authorization: Bearer $PITCHSTATION_TOKEN" -H 'Content-Type: application/json' \
-d '{"text":"YOUR_COMPANY is a Kaohsiung studio that designs…"}'
# 2. build the site; the logo is a data: URI
curl -X POST https://pitchstation.ai/api/website/generate \
-H "Authorization: Bearer $PITCHSTATION_TOKEN" -H 'Content-Type: application/json' \
-d '{"content":{…from step 1…},"assets":{"logo":"data:image/png;base64,…"},
"external_ref":"crm-1042"}'
# 3. save the intended server and address BEFORE review
PUT /api/website/<deckId>/domain {"subdomain":"harbour-c","targetId":3}
# For a full external domain, complete the returned TXT ownership proof and save again.
# 4. send for approval; after the customer approves, publish to the SAME target/address
POST /api/website/<deckId>/submit-review {"approverEmail":"APPROVER_EMAIL"}
POST /api/website/<deckId>/publish {"targetId":3,"dryRun":false}
Re-sending the same external_ref returns the existing site instead of making a duplicate, so a retry is safe. A changed canonical address needs a new approval; SITE_URL_REVIEW_REQUIRED means save the address with the intended target and re-submit for review. The full schema is in the Website OpenAPI; the API reference gives a shorter overview.
GET /api/website/templates lists the classic templates and the style families your account may pick (partner templates only under their lock), each family with its names, palettes, sectionIds, defaultOrder, industries and brand_fields (the meta.brand fields it reads). Set content.meta.template and meta.palette; a missing palette is the family's default. Ask the catalog instead of hard-coding the list./extract drafts carry style_suggestion beside content, images and warnings. For any content, POST /api/website/suggest-style (websites:write, read-only) takes {content}, {deckId} or {logo} and answers {style_suggestion: {family, palette, alternatives, accent, accent_check, logo, reasons, ranking}}: alternatives names zero to two more families, each with a reason of its own (in ranking), never one picked just to fill the list; logo is none, colour, monochrome or unreadable; reasons are INDUSTRY, KEYWORDS, SHAPE and PALETTE_COLOUR, and family is null with NO_SIGNAL when nothing points anywhere. The palette follows the brand colour in this order: partner lock, meta.brand.accent, the logo, the account's accent. meta.industry_key must be one of the GA families' industries (the list only grows). Nothing is written: apply a suggestion yourself. The editor's From the logo uses the same route.POST /api/website/style-gallery (content or a deckId, optional assets, device desktop or phone, optional options) answers 202 {jobId, items} while thumbnails are on; poll GET /api/website/style-gallery/jobs/<id> and fetch GET /api/website/style-gallery/thumb/<id>. With thumbnails off it answers 200 {thumbnails: false, reason, items}: render live previews from items. POST /api/website/style-gallery/link makes the one-hour phone link (/s/_sp/<token> on the content origin, an SVG qr, expiresAt, retired, maxLinks); DELETE /api/website/style-gallery/link/<token> closes it. GET /api/website/families/<id>/demo?palette=<palette> renders a family on its own sample content.POST /api/website/preview renders exactly what a save would (pass deckId for a saved site: its owner's lock and brand; SECTIONS_DROPPED as on /update) and refuses what a save refuses, including 400 BAD_VIDEO_URL; a style family whose pack is unavailable on the server answers 422 first. Its notes come in the X-Render-Warnings and X-Font-Warnings headers (§04).POST /api/website/<deckId>/submit-review with style_options: [{template, palette}, …]: two or three styles, option 1 the site's current one, distinct after the partner lock. The answer's styleOptions[i].warnings are each option's render notes; they are not stored. A set that cannot be offered is 400 BAD_STYLE_OPTIONS {option, reason, path} (a video only a family plays, on a classic option, is reason: "BAD_VIDEO_URL", path: "video.url"); a site without a saved logo is 409 LOGO_REQUIRED. Each user may send WEBSITE_STYLE_OPTIONS_PER_HOUR such submissions an hour (20 by default, counted when the rendering starts, per server process); over it: 429 STYLE_OPTIONS_RATE_LIMITED with Retry-After. The reviewer's link serves option n at ?style=n and chooses with POST /s/<slug>/choose-style {idx, revisionId, epoch}: 400 BAD_STYLE_OPTION, 404 STYLE_OPTION_UNKNOWN, 409 REVIEW_CHANGED (reload), 403 REVIEWER_REQUIRED, 409 STYLE_LOCK_CHANGED (submit again) or 429 STYLE_CHOICE_RATE_LIMITED. Choosing the style already under review answers 200 {unchanged: true}.website.style_chosen fires with the team's notice, once per burst of choices, carrying the latest one: deckId, external_ref, metadata, idx, template, palette, revisionId, epoch, round and chosen_by. It is not an approval: publish on website.approved. The notice timer lives in the server process, so a restart inside the window loses that event.For whoever runs the PitchStation server; every setting is in .env.example.
WEBSITE_STYLE_THUMBS=1 makes server-side thumbnails with the PDF renderer's Chromium; off (the default) or unavailable, the gallery shows live previews. Caches and caps: WEBSITE_THUMB_DIR (temp/website-thumbs), WEBSITE_THUMB_CACHE_MB (256), WEBSITE_THUMB_CACHE_FILES (4,000), WEBSITE_THUMB_USER_JOBS (2), WEBSITE_THUMB_USER_ITEMS_PER_HOUR (300), WEBSITE_THUMB_MAX_JOBS (8), WEBSITE_THUMB_TIMEOUT_MS (30,000). Phone links: WEBSITE_PHONE_PREVIEW_DIR (temp/website-phone-previews), WEBSITE_PHONE_PREVIEW_MAX_LINKS (5 per user), WEBSITE_PHONE_PREVIEW_USER_MB (24). Family demos are cached in memory up to WEBSITE_DEMO_CACHE_MB (48). All of these are temporary: a host move or a restore drops them, and the editor makes new ones.WEBSITE_STYLE_CHOICE_RATE (12 choices per 10 minutes per review link and client, failed ones included), WEBSITE_STYLE_CHOICE_NOTIFY_MS (90,000: the notice waits this long after the first choice) and WEBSITE_STYLE_OPTIONS_PER_HOUR (20).node scripts/website-fonts-fetch.cjs into FONT_SOURCE_DIR (default vendor/font-sources; the Docker image fetches them itself). Without them a production server refuses family renders with 503 FONTS_UNAVAILABLE; WEBSITE_FONTS_OPTIONAL=1 lets them fall back to system fonts and report fontWarnings instead.WEBSITE_LEGACY_VISUAL_FIXES=1 (exactly 1; off by default, read on every render) turns on visible fixes of the eight classic templates; style families are not affected, and with it off classic pages stay byte for byte as before. It fixes five broken clamp() sizes, Volt's font name, Executive's colours showing through on the other templates, Runway's and Bridgelink 360's unreadable dark bands, the hero art's entrance animation, the scroll cue on phones (120 px of hero padding above and below), Simplified Chinese faces on zh-Hans pages, a brand accent reaching the calls to action (on Runway's dark grounds only an accent of 3:1 or more against #161616), the WeChat popover staying closed until opened, and a <meta name="theme-color"> that defaults to the template's own navy when the content sets none (a stored meta.theme_color is kept). Bridgelink 360 is a partner template whose dark bands then show its blue as #8FB2F2: agree that with the partner before switching on. A known limit: an announcement bar of three or more lines on a narrow phone still reaches the logo on text-first heroes. Pages change when they are next rendered and published.| You see | What it means / what to do |
|---|---|
| “…took too long to respond” | The connection dropped while a brochure was being read. Upload it again; very large PDFs go faster split into the pages that matter. |
| “…expired or the server restarted; upload again” | The server restarted while it was reading your file. Upload it again. |
| No text found / scanned PDF | The PDF is pictures of pages. Type a description, or photograph the pages in the mobile app. |
| Too many uploads at once | Up to five brochures can be read at the same time per account. Wait for one to finish. |
Video link refused (BAD_VIDEO_URL) | The style cannot play it. Its reason: SHORT_LINK (a b23.tv or other short link: paste the full page link), SERIES_LINK (a Tencent Video series page: open the episode and paste its link), INSECURE (an http:// .mp4: use https://) or UNSUPPORTED. Classic templates play only YouTube and Vimeo. |
| Style suggestion refused | 400 BAD_CONTENT, BAD_LOGO or NOTHING_TO_SUGGEST: send valid content, an accessible saved deckId or a logo. A missing saved site is 404; 413 SUGGEST_INPUT_TOO_LARGE means the content holds more than 32 MB. |
BAD_CONTENT or ASSET_TOO_LARGE | Content nested deeper than 1,000 levels is refused on every content route. A logo or icon longer than about 9.2 million characters is refused before it is decoded; photos of any size are resized to 1,600 px instead (a request may carry 110 MB in all). |
FONTS_UNAVAILABLE (503) | The server cannot prepare a style family's fonts. Try again in a moment; if it persists, the operator installs the font sources (§10). |
| The client cannot choose a style | REVIEWER_REQUIRED: sign in as the reviewer the link was sent to. REVIEW_CHANGED: reload the page. STYLE_LOCK_CHANGED: your partner lock changed, so submit the review again. STYLE_CHOICE_RATE_LIMITED: wait a few minutes. |
| AI allowance used up | You've made 60 AI requests today. Carry on editing by hand; it resets tomorrow. |
| Name already taken | Site names are unique across PitchStation. Pick another, or use your own domain. |
| Publish refused: approval required | The current version hasn't been approved. Submit it for review (§05) and publish after the client approves. |
| Publish refused: email not verified | Click the verification link in your welcome email, then try again. |
| Live deploys are disabled on this server | Your administrator hasn't switched live publishing on. Download the .zip bundle meanwhile. |
| A site or daily-publish limit | Your plan caps how many sites you keep and how often you publish a day. Delete an old test site, or ask your platform contact. |