EdgazeEdgaze Docs
Builder
Home
Overview of all Edgaze documentation.
Builder Overview
A complete beginner-friendly guide to the Edgaze builder system, including Workflow Studio, Prompt Studio, Templates, and API Vault.
Workflow Studio
A complete Workflow Studio guide covering the canvas, builder flow, and every node available in Edgaze.
Prompt Studio
Learn how to create reusable prompt products in Edgaze, from placeholders and testing to publishing and monetization.
Templates
Learn how Edgaze templates work, how guided setup flows create editable workflows, and how to start from outcomes instead of raw nodes.
API Vault
Learn how the Edgaze API Vault stores provider keys, how nodes use vault-backed access, and how to set up reliable provider execution.
Resources
Changelog ✨
Product updates, platform changes, and notable improvements.
Privacy Policy
How Edgaze collects, uses, and handles information.
Terms of Service
The core platform terms that govern access to Edgaze, including product usage, publishing, platform limitations, and legal responsibilities.
Creator Terms
The terms that apply to creators who publish and monetize products on Edgaze, including payouts, responsibilities, and marketplace conduct.
Acceptable Use Policy
Rules governing permitted and prohibited use of the Edgaze platform.
DMCA and Intellectual Property Takedown Policy
Procedure for reporting copyright and intellectual property infringement on Edgaze.
Community Guidelines
Legally framed standards governing conduct, content, comments, and participation on the Edgaze platform.
Payments Overview
A beginner-friendly guide to how customers pay, how creators earn, and how money moves through Edgaze.
Payout System
Learn how the Edgaze payout system works, including sell now onboard later, creator eligibility, and the role Stripe plays in payout release.
Marketplace Fees
How Edgaze marketplace fees are calculated and applied
Creator Earnings
Learn how creator earnings are attributed, what 80/20 means in practice, and how to think about sales, balances, refunds, and payout readiness.
Workflow Run Policy
Hosted runs, consumption rules, and options after runs are used
Infrastructure Cost Estimation
Learn how infrastructure cost guidance works in Edgaze publishing and why it is there to help creators price responsibly.
Refund Policy
Our refund policy for workflow and prompt purchases
Chargeback Policy
How Edgaze and creators handle payment disputes and chargebacks
Creator Subscription Policy
Edgaze Plus subscription benefits and terms for creators
Pricing Limits
Minimum and maximum price rules for prompts and workflows
Fraud and Abuse Policy
How Edgaze prevents and responds to fraud and abuse
Content Disclaimer
Important disclosures regarding content available on the Edgaze platform.
Platform Status and Beta Disclaimer
Important disclosures regarding the beta status of the Edgaze platform.
Security and Responsible Disclosure
Guidelines for reporting security vulnerabilities and bugs affecting the Edgaze platform.
Creator Guidelines
Standards and rules for creators publishing content on the Edgaze platform.

Templates

Learn how Edgaze templates work, how guided setup flows create editable workflows, and how to start from outcomes instead of raw nodes.

Templates

Templates are the fastest way to start building in Edgaze when you know the result you want but do not want to assemble a graph from scratch.

Instead of asking you to think in nodes first, templates let you think in outcomes first.

On This Page

  • What templates are
  • Where templates appear
  • How guided setup works
  • What happens after you click Use template
  • Example template structure
  • When to use templates vs blank builder

What Templates Are

Definition Layer

A template has its own metadata, preview, setup schema, and workflow blueprint.

Instantiation Layer

The final workflow is created from the template definition and the user's answers.

A template is not just a copied workflow file.

A template in Edgaze is a structured system with:

  • product metadata
  • a preview graph
  • a guided setup schema
  • an underlying workflow blueprint
  • deterministic instantiation rules

That matters because the workflow created from a template still needs to be reliable, editable, and easy to understand once it lands in the builder.

Where Templates Appear

Standalone Library

The `/templates` route is for discovery, browsing, and detail-page evaluation.

Builder Modal

The in-builder modal is for fast insertion while a creator is already working.

Templates appear in two places:

  • the standalone library at `/templates`
  • the template modal inside Workflow Studio

These are two entry points into the same underlying template system. They should feel like the same product surface because they are reading from the same source of truth.

How Guided Setup Works

Outcome First

The user should answer outcome-focused questions before seeing the final graph.

Setup Before Builder

This reduces low-level builder work and makes the workflow feel immediately usable.

Some templates can be used instantly. Others ask a few setup questions first.

The right experience is:

  1. Choose the template.
  2. Answer a small number of guided questions.
  3. Let Edgaze build the initial workflow for you.
  4. Open that workflow in Workflow Studio as a normal editable graph.

This is important because good template UX should absorb complexity before the builder opens.

Guided Setup Should Feel Like Product, Not Dev Tooling

A strong setup step asks questions like:

  • How many inputs should this workflow use?
  • What should the prompt optimiser focus on?
  • Which model should this use?
  • What output shape do you want?

It should not force the user to understand:

  • node configuration paths
  • handle mapping
  • raw internal prompt plumbing

Good Guided Questions

Good setup questions explain the decision in the language of the outcome.

Bad Guided Questions

Bad setup questions expose internal graph mechanics that should stay abstracted.

What Happens After You Click Use Template

After guided setup is complete, Edgaze instantiates a real workflow from the template definition.

That generated workflow:

  • uses normal builder primitives
  • appears in Workflow Studio as a normal graph
  • can still be edited block by block afterward

Templates are meant to accelerate creation, not hide the workflow forever.

Editable After Generation

The generated workflow should still be inspectable and editable in Workflow Studio.

Example: AI Art Creator

AI Art Creator is a guided creative workflow template.

Its guided setup can ask for:

  • number of inputs
  • the question and format for each input
  • prompt optimiser instructions
  • image model
  • aspect ratio

The resulting workflow can look like this:

Workflow Preview

AI Art Creator

Read-only builder graph

Press enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

If the selected input count is three or fewer, the graph can stay simpler and use one merge path instead of two.

Why This Graph Works

It keeps the input gathering layer separate from the optimisation and generation layer.

Template Detail Pages

What A Detail Page Should Explain

A detail page should make the workflow understandable before the builder opens.

What A Detail Page Should Avoid

It should avoid dumping raw internal implementation detail onto the user.

Template detail pages exist so a user can evaluate the product before opening the builder.

A good detail page should answer:

  • what this template creates
  • what setup the user will be asked for
  • what the graph shape looks like
  • what kind of creator or use case it is best for

The page is not there to overwhelm the user with every internal configuration detail.

When To Use Templates

Templates are the best choice when:

  • the user wants a working starting point fast
  • the outcome is more important than the graph structure
  • setup questions can remove the need for manual builder work

Templates are less important when:

  • you already know the exact graph you want
  • the workflow is small enough to build directly
  • you are experimenting with low-level logic from scratch

Best Use Case

Templates are strongest when they remove repetitive setup work from a known product pattern.

Best Practices For Template-Based Products

  • Start with a strong outcome name.
  • Keep setup steps short and guided.
  • Use the same visual language in the modal and page.
  • Make the generated workflow readable after insertion.
  • Keep the graph editable after setup.

Reliability Principle

The template system should instantiate workflows predictably rather than relying on brittle graph cloning.

What To Read Next

  • Workflow Studio
  • API Vault
  • Builder Overview
On this page
On This PageWhat Templates AreDefinition LayerInstantiation LayerWhere Templates AppearStandalone LibraryBuilder ModalHow Guided Setup WorksOutcome FirstSetup Before BuilderGuided Setup Should Feel Like Product, Not Dev ToolingGood Guided QuestionsBad Guided QuestionsWhat Happens After You Click Use TemplateEditable After GenerationExample: AI Art CreatorWhy This Graph WorksTemplate Detail PagesWhat A Detail Page Should ExplainWhat A Detail Page Should AvoidWhen To Use TemplatesBest Use CaseBest Practices For Template-Based ProductsReliability PrincipleWhat To Read Next
© 2026 Edge Platforms, Inc. All rights reserved.