Marketplace and stacks

A stack is an installable bundle of things you've built on FYAI — agents, teams, functions, workflows, data sources, dashboards, elements and programs — packaged so that someone else can deploy a working copy into their own project in a couple of clicks.

The Marketplace is where you find, install and publish stacks. Open it from Marketplace at the bottom of the sidebar. Any member of an organisation can browse, install and publish.

The Marketplace has three tabs:

Tab	Address	Use it to
Browse	/marketplace	Find stacks to install.
Create a Stack	/marketplace/build	Bundle your own components and publish them.
Installed	/marketplace/installed	See what you've installed and uninstall it.

Select How Stacks work at any time for a short explainer.

What's in a stack

A stack contains a blueprint of each component, and a list of requirements the installer must fill in.

• Components. Agents, teams, functions, workflows, data sources, dashboards, elements and programs. Manifests and integrations can also be included when other components depend on them.
• Dependencies come along automatically. Add a team and its agents come too; add an agent and its functions come too; add a workflow and the agents, teams, functions and elements it uses come too.
• Requirements. Things the installer supplies from their own organisation:
  • LLM model — every agent needs one of the installer's own models.
  • Integration — functions and data sources that need credentials are connected to the installer's own integrations.

Secrets never travel with a stack

API keys, tokens, passwords and other credentials are stripped when a stack is published. Anything secret becomes a requirement the installer fills with their own.

Browse stacks

The Browse tab lists every stack published publicly, plus your own organisation's stacks.

• Search by stack name or summary.
• Sort by Most installed (default), Newest or Top rated.
• Filter by category, by component type (Contains:), and by Free or Paid.

Each tile shows the stack's cover, category, publisher, how many organisations use it, a summary, what it contains, its tags and the latest version. Select a tile to open the stack's page, or Install to install straight away.

When your organisation hasn't installed anything yet, a Popular first stacks row suggests good starting points.

The stack page

A stack's page shows its description and:

• What's inside — every component, grouped by type
• You provide at install — the requirements, or "None — installs with no inputs"
• the price, the number of components and requirements, the last update date and the publisher

Install a stack

A stack installs into your current project, so switch to the right project first.

1. Select Install on the tile or the stack page.
2. FYAI checks what the stack needs. For each requirement, choose one of your own:
   • LLM model — pick one of your configured models. If you have none, create one first (see Models).
   • Integration — pick one of your integrations.
3. Select Install.

When it finishes, FYAI lists everything it created, with links to each item. From there you can View installed, open a new dashboard if the stack had one, or start a chat with the stack's lead agent.

The Install button stays disabled until every requirement has a value and you have a current project.

OAuth apps for Xero, Microsoft and similar providers

Some connectors, for example Xero, Atlassian and Microsoft, sign people in through an app registered once per organisation. When a stack includes one:

• If your organisation already has the app registered, the install dialog says so and reuses it.
• If not, the dialog shows step-by-step instructions for registering the app with the provider, the Redirect URI to use, and Client ID and Client secret fields.

note

Registering a provider app for the first time is restricted to administrators. If your install stops with a message asking an administrator to register the app, contact FYAI support.

Once the app is registered, each person connects their own account. See Connected accounts.

What an install creates

• Fresh copies. Everything is created new in your project and is yours to change. Nothing you already have is overwritten.
• Name clashes. If an agent, team, function or integration with the same name already exists in the project, the new one gets a short suffix. Other component types can end up with duplicate names.
• Installing again creates another full set of copies.
• Dashboards from a stack are created as your own dashboards. Data sources are created as personal data sources.
• Workflow schedules aren't included. Set up any schedules you need after installing. See Scheduling workflows.
• Credentials. Integrations brought in by a stack have no secrets; connect them or enter credentials before use.

If an install fails part-way, it's marked partial and whatever was created stays in your project.

Installed stacks

The Installed tab lists your organisation's installs: the stack and version, when and into which project it was installed, what it created, and its status (installed, partial, pending or failed).

• Open assistant opens a chat with the stack's lead agent.
• Uninstall removes the install.

warning

Uninstall deletes every component the install created, including any changes you've made to them since, and there is no confirmation step. Copy anything you want to keep first.

Uninstalled stacks are hidden; select Show uninstalled to see them.

Installed copies don't update when the publisher releases a new version. To get a newer version, install it again.

Create and publish a stack

Open Create a Stack. The builder has three steps.

1. Describe

Field	Notes
Name	Required. What people see in the marketplace.
Summary	One line shown on the tile.
How to use this stack	Shown on the stack page: what it does, what installers should do after deploying, and what the requirements are for.
Category	Pick a suggestion (Sales, Marketing, Support, Research, Operations, Finance, Data & Analytics, Engineering, Productivity) or type your own.
Tags	Press Enter after each tag.
Cover art	Optional: an emoji, a Custom icon URL or a Banner image URL. Without art, a cover is generated.
Visibility	Private, Organisation, Link only or Public. See below.
Pricing	Free or Paid with a Price (USD).

Select Save & pick components.

2. Pick components

Tick the components to include. Search with Search your components…. Dependencies are added automatically, and FYAI checks the bundle as you go:

• Ready to publish shows how many components there are, how many were added automatically, and how many requirements installers will provide.
• A warning appears if the bundle can't be published, for example if it's empty, has a dependency cycle, or would contain an embedded secret.

You can only bundle components from your current project. Dashboards and personal data sources can only be bundled by their owner.

3. Review & publish

Check what ships and what installers bring, enter a Version in X.Y.Z form (for example 1.0.0) and an optional Changelog, then select Publish v....

Visibility

Option	Who can see and install it
Private	Your organisation (see note).
Organisation	Everyone in your organisation.
Link only	Anyone with the share code shown after publishing.
Public	Everyone, listed in the marketplace.

note

At present, Private stacks are visible to everyone in your organisation, the same as Organisation. Link only stacks can't yet be opened from a share link in the app; the share code works through the Platform API.

Limits of the builder today

• Each run of the builder creates a new stack. You can't edit a published stack, publish a new version of it, or withdraw it from the app.
• Paid stacks show a price but nothing is charged at install.
• Star ratings are displayed where present, but there's no way to rate a stack yet.

Related

• Templates — platform-provided resources in every project
• Promoting between projects — copy your own teams and workflows between projects
• Agents, Workflows, Dashboards