Skip to main content

Introduction to Projects

Fynd Boltic Projects are organizational workspaces that bring your platform resources together under one roof. Instead of managing workflows, gateways, tables, and other entities separately, you can group them into a project with a name, description, and team-facing overview—then manage, navigate, and collaborate on everything from a single project dashboard.

Projects are ideal when you are building a product feature, customer integration, or internal automation that spans multiple Boltic services. A single project might contain the workflow that orchestrates data, the gateway that exposes APIs, the tables that store records, and the serverless functions that handle custom logic.

Key features

  • Unified workspace — View and manage all resources tied to a business initiative from one project page.
  • Multi-entity support — Associate workflows, gateways, serverless apps, database tables, MCP servers, and AI agents with a project.
  • Guided project creation — Use a step-by-step wizard to name your project, add a description, and optionally link existing entities at creation time.
  • Project templates — Bootstrap projects from approved blueprints or publish your own project as a reusable template. See Project templates.
  • Entity tabs — After creation, each entity type gets its own tab with a full listing, search, and actions—matching the experience you already know from standalone listings.
  • Team overview — Add a markdown readme on the Overview tab so teammates understand scope, architecture, and runbooks.
  • Flexible deletion — Delete only the project container, or delete the project and all associated entities in one action.
  • Search and filters — Find projects quickly on the listing page with name search, entity-type filters, and creator/modifier filters.

Supported entity types

A project can contain the following Boltic resources. Each type appears as a dedicated tab inside the project once at least one entity of that type is linked.

Entity typeDescriptionLearn more
WorkflowsVisual automations built in the Workflow BuilderWorkflow docs
AI AgentsKaily copilots and agents (opens in Kaily console)AI Agent Setup
GatewayAPI gateways for routing and securing trafficGateway docs
ServerlessDeployed serverless applicationsServerless docs
Database TablesStructured data stored in Boltic TablesDatabase docs
MCPModel Context Protocol servers and actionsMCP docs
note

Analytics is visible on the project details page but is not yet available. The tab is marked as coming soon.

How projects relate to entities

A project does not replace individual services—it organizes references to them. When you add a workflow to a project, the workflow continues to live in the Workflow Builder; the project stores the association so you can find and open it from the project context.

You can:

  • Add existing entities that were created outside the project.
  • Create new entities from within a project, which automatically associates them with that project.
  • Remove an entity from a project without deleting the underlying resource—the entity remains available elsewhere in your account.

Deleting a project gives you two choices: remove only the project structure, or delete the project and all linked entities permanently. See Deleting a project for details.

When to use projects

Use projects when you want to:

  • Group everything for a customer deployment, product launch, or internal tool.
  • Give teammates a single entry point with documentation in the Overview tab.
  • Track which workflows, gateways, and tables belong to the same initiative.
  • Create new serverless apps or gateways in context so they are linked to the right project from the start.

What's next?