Home/HighLevel/Features/AI Employee/HighLevel AI Studio full stack: SSR, server functions and APIs

AI

HighLevel AI Studio full stack: SSR, server functions and APIs

In short

AI Studio now supports full stack applications with server side rendering, Server Functions, REST APIs and secure Secrets. Teams can efficiently build both the public interface and the private backend in a single project and deploy it through the platform’s publishing workflow.

AreaAI Employee · AI Studio
Used forEcommerce store, Marketing agency, SaaS platform
Setup steps39 steps in 8 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Founders who need to combine a public website with private backend logic to avoid maintaining separate codebases.
  • Developers building integrations that require hidden API keys or webhook endpoints within a HighLevel application.

02AI Studio full stack features, explained

The full stack features let a project generate HTML on the server (SSR), run private code accessed only by the frontend (Server Functions), expose HTTP endpoints for external services (REST APIs), and keep credentials out of client bundles (Secrets). All of these capabilities live inside a single AI Studio project and are managed through the platform’s UI.

When a new project is created, it automatically uses the TanStack Start architecture that supports these features. Existing Vite/React projects keep their original setup and do not switch to the new stack unless you run a separate migration.

Publishing the project makes the combined frontend and backend available at a generated URL, and a custom domain can be attached afterward.

03How businesses use AI Studio full stack features

  • Ecommerce store. The store adds a Secret for the payment gateway key, creates a Server Function that processes orders using that key, and builds a REST API endpoint to receive order status webhooks. All logic runs on the server, keeping credentials hidden.
  • Marketing agency. The agency builds a landing page that uses SSR for SEO, adds a Server Function to fetch client specific data with a stored Secret, and publishes the site. A custom domain is attached so clients see the agency branded URL.
  • SaaS platform. The platform defines a REST API route for external applications to request usage data, secures the endpoint with authentication, and stores the API token as a Secret. The API is tested in the preview mode before the platform is published.

04How to set up and use AI Studio full stack features in HighLevel

Create a new AI Studio project

  1. Open the applicable HighLevel subaccount.
  2. Select AI Studio from the left navigation.
  3. Click to create a new project.
  4. Enter a description of the website or application you want built.

Describe the full application behavior

  1. Specify what the application must do, not only how it should look.
  2. Mention any external services, private credentials, incoming webhooks, protected processing, and public API requirements.

Add Secrets for protected credentials

  1. Identify the private credential required by the integration.
  2. Open the Secrets workflow when prompted.
  3. Enter a clear, recognizable name for the Secret.
  4. Save the Secret value.
  5. Reference the Secret only from server side code and test without exposing it to the browser.

Build and review Server Functions

  1. Write the server side logic that the frontend will call.
  2. Ensure any sensitive processing runs on the server.
  3. Retrieve required private values from Secrets.
  4. Return only the data needed by the frontend.
  5. Test both successful and error paths and review the generated code for further validation.

Create REST APIs for external requests

  1. Define the API endpoint path.
  2. Choose the supported HTTP method.
  3. Specify the expected request payload format.
  4. Add authentication or signature validation if required.
  5. Implement server side processing of the request.
  6. Return the appropriate response to the caller.

Preview and test the application

  1. Verify that public pages load as expected.
  2. Test Server Functions with valid and invalid inputs.
  3. Call REST endpoints with the intended request data.
  4. Confirm that Secrets never appear in browser output.
  5. Check that error states are handled safely.
  6. Review page titles, headings and metadata.

Publish the application

  1. Click the Publish button.
  2. Review or update the generated website address.
  3. Confirm the publication action.
  4. Open the live URL and verify the application works.

Connect a custom domain

  1. Open the Publish panel.
  2. Choose Add Custom Domain.
  3. Enter the domain you want to use.
  4. Add the DNS records supplied by AI Studio at your domain provider.
  5. Click Verify DNS.
  6. Allow certificate provisioning to complete.
  7. Test the application through the connected domain.

05What it looks like in HighLevel

06Settings that matter

  • Server, Side Rendering (SSR). Controls whether page HTML is generated on the server before it reaches the browser.
  • Server Functions. Enables private backend logic that the frontend can call without exposing the code to the client.
  • REST APIs. Creates HTTP endpoints that external services can invoke.
  • Secrets. Stores API keys, tokens and other sensitive values on the server side, keeping them out of client bundles.

07Things to know before you rely on it

  • The private beta for full stack features has ended; all new projects use the TanStack Start architecture.
  • Existing Vite/React AI Studio projects continue using their original architecture and are not automatically migrated.
  • A separate migration process is required for an existing project to adopt the new full stack stack.

08If something goes wrong

  • Server Function fails. Review the function inputs, required Secrets, any server side errors and the data returned to the frontend.
  • REST endpoint cannot be called. Confirm the endpoint path, HTTP method, published application state, request format and any authentication requirements.
  • External API authentication fails. Make sure the correct Secret exists and that server side code references the intended value.
  • Webhook requests fail verification. Verify the signing Secret, request headers, signature validation logic and the callback URL.
  • Custom domain does not load. Confirm the DNS records exactly match the values provided by AI Studio and run Verify DNS after propagation.
  • Existing project does not show new architecture behavior. Check whether the project was created using the earlier Vite/React architecture; existing projects are not automatically migrated.

09How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

People often think the full stack tools are only for large apps, so they jump straight into SSR or REST routes without first mapping out what truly needs to stay private. That adds unnecessary public endpoints and makes the project harder to maintain.

I would begin with sketching the exact flow: Which pages must be indexed, which operations need a secret key, and which external services will call in. Then I add a Secret, build a Server Function for the private call, and only create a REST API if an outside system really needs to reach you. Test each piece locally before you hit Publish.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about AI Studio full stack features.

Do existing AI Studio projects automatically move to TanStack Start?

No. Existing Vite/React projects keep their current architecture and are not automatically migrated.

What is the difference between a Server Function and a REST API?

Server Functions are used when the application's own frontend needs private backend logic, while REST APIs expose HTTP endpoints for external systems.

Can a Server Function use a Secret?

Yes. Server Functions commonly reference Secrets to keep private credentials out of the client bundle.

Can I create webhook endpoints in AI Studio?

Yes. REST API routes can be defined to accept webhook calls from supported providers.

Should I put a Secret directly in frontend code?

No. Secrets must remain on the server and be accessed only by server side functionality.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.