能力标签

🤖 Agent 🔄 工作流 🌐 翻译 🐳 Docker 💻 CLI 🔗 REST API

⚙️

Agent工作流

开源AI工作流

基于 TypeScript · 无代码搭建完整 AI 自动化流程

英文名：saas-starter

⭐ 37 Stars 🍴 9 Forks 💻 TypeScript 📄 未公布协议 🏷 AI 8.0分

8.0AI 综合评分

ai-chatbetter-authconvextypescript

⚙️ 配置说明 🔍 查看原项目

✦ AI Skill Hub 推荐

经 AI Skill Hub 精选评估，开源AI工作流获评「强烈推荐」。这款Agent工作流在功能完整性、社区活跃度和易用性方面表现出色，AI 评分 8.0 分，适合有一定技术背景的用户使用。

📚 深度解析

开源AI工作流是一套完整的 AI Agent 自动化工作流方案。随着 AI 能力的不断提升，基于 Agent 的自动化工作流正在成为提升个人和团队效率的核心方式。区别于传统的 RPA 自动化（模拟鼠标键盘操作），AI Agent 工作流通过理解任务意图、动态规划执行路径，能够处理更复杂的非结构化任务。

开源AI工作流工作流的设计遵循"最小配置，最大复用"原则：核心逻辑已经封装好，用户只需配置自己的 API Key 和业务参数即可快速上手。工作流内置错误处理和重试机制，在网络波动或 API 限速等情况下仍能稳定运行，适合作为生产环境的自动化基础设施。

在实际部署时，建议先在测试环境中运行 3-5 次，验证各个环节的输出结果符合预期，再部署到生产环境。AI Skill Hub 评分 8.0 分，是同类 Agent 工作流中的精选推荐。

📋 工具概览

开源AI工作流是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。

GitHub Stars

⭐ 37

开发语言

TypeScript

支持平台

Windows / macOS / Linux

维护状态

轻量级项目，按需更新

开源协议

未公布

AI 综合评分

8.0 分

工具类型

Agent工作流

Forks

📖 中文文档

以下内容由 AI Skill Hub 根据项目信息自动整理，如需查看完整原始文档请访问底部「原始来源」。

📌 核心特色

可视化 Agent 工作流编排，无需编写复杂代码
支持多步骤自动化任务链，实现全流程无人值守
与外部 API、数据库和第三方服务无缝集成
内置错误处理与自动重试机制，保障稳定运行
提供可复用的自动化模板，快速在同类场景部署

🎯 主要使用场景

自动化日常重复性工作，将精力集中于创造性任务
构建数据采集 → 处理 → 输出的完整自动化管线
实现跨平台、跨系统的数据流转和业务协同

以下安装命令基于项目开发语言和类型自动生成，实际以官方 README 为准。

安装命令

# 方式一：npm 全局安装
npm install -g saas-starter

# 方式二：npx 直接运行（无需安装）
npx saas-starter --help

# 方式三：项目依赖安装
npm install saas-starter

# 方式四：从源码运行
git clone https://github.com/stickerdaniel/saas-starter
cd saas-starter
npm install
npm start

📋 安装步骤说明

访问 GitHub 仓库获取工作流文件
在对应平台（Dify / Flowise / Make 等）中找到「导入工作流」功能
上传工作流文件
按照提示配置必要的环境变量和 API Key
运行测试确认流程正常后投入使用

以下用法示例由 AI Skill Hub 整理，涵盖最常见的使用场景。

常用命令 / 代码示例

# 命令行使用
saas-starter --help

# 基本用法
saas-starter [options] <input>

# Node.js 代码中使用
const saas_starter = require('saas-starter');

const result = await saas_starter.run(options);
console.log(result);

以下配置示例基于典型使用场景生成，具体参数请参照官方文档调整。

配置示例

# saas-starter 配置说明
# 查看配置选项
saas-starter --config-example > config.yml

# 常见配置项
# output_dir: ./output
# log_level: info
# workers: 4

# 环境变量（覆盖配置文件）
export SAAS_STARTER_CONFIG="/path/to/config.yml"

📑 README 深度解析真实文档完整度 55/100 查看 GitHub 原文 →

以下内容由系统直接从 GitHub README 解析整理，保留代码块、表格与列表结构。

SaaS Starter

A free, open-source SaaS template built with SvelteKit, Convex, Better Auth, Tolgee, and Tailwind. Auth, billing, admin, AI chat, email, and i18n are all implemented end-to-end so you and your AI agents have real patterns to build on. Deploy on Cloudflare Workers or Vercel for $0.

See a live demo of the user-facing side at saas.daniel.sticker.name. Admin features like the admin panel, support dashboard, and user management are not accessible there. To explore everything, follow the steps below.

Dependency Automation

Renovate groups non-major updates into a single PR and creates separate PRs for packages that tend to ship breaking changes (Better Auth, AI SDK, ESLint), so upgrades are easier to review.

Preview Deployments

Each PR gets its own preview deployment with an isolated Convex preview backend. Supports both Cloudflare Workers and Vercel.

Create a Convex project at dashboard.convex.dev and connect your repo to your hosting platform.

The deploy script (scripts/deploy.ts) auto-detects the platform from environment variables (WORKERS_CI, CF_PAGES, or VERCEL), tags and pulls translations, runs bunx convex deploy to create a preview backend named after the branch, auto-computes PUBLIC_CONVEX_URL and PUBLIC_CONVEX_SITE_URL from the deploy output, and sets SITE_URL on the Convex instance to match the preview URL. When PREVIEW_ADMIN_PASSWORD is set, it also seeds an admin user.

<details> <summary>Cloudflare Workers setup</summary>

Deploy via Cloudflare Workers with Workers Builds:

1. Create Worker

Rename name in wrangler.toml to your project name
Run bunx wrangler deploy (first deploy creates the Worker)

2. Connect repo

CF dashboard > Workers & Pages > select Worker > Builds > Connect
If the repo isn't visible: GitHub Settings > Applications > Cloudflare Workers and Pages > Configure > grant repo access

3. Configure build commands

Field	Value
Build command	`bunx varlock run -- bun scripts/deploy.ts`
Deploy command	`bunx wrangler deploy`
Non-production branch deploy command	`bun scripts/cf-deploy.ts`

4. Add build variables (plain text, visible in logs)

Variable	Value	Notes
`WORKERS_NAME`	Name from `wrangler.toml`	Required for preview URL construction
`WORKERS_SUBDOMAIN`	Account subdomain (e.g., `daniel-ce4`)	Visible at Workers & Pages overview as `*.workers.dev`
`SITE_URL`	`https://your-domain.com`	Production custom domain. Ignored for previews (URL is auto-constructed from `WORKERS_NAME`/`WORKERS_SUBDOMAIN`). Falls back to `workers.dev` URL if unset.

5. Add build secrets (encrypted, hidden from logs)

Secret	Where to find it
`CONVEX_DEPLOY_KEY`	Convex dashboard > Project Settings > Production Deploy Keys
`CONVEX_PREVIEW_DEPLOY_KEY`	Convex dashboard > Project Settings > Preview Deploy Keys

6. Set Convex default env vars for previews

Each preview Convex deployment starts with no env vars. Set defaults in Convex dashboard > Project Settings > Default Environment Variables with only Preview/Development checked (not Production):

BETTER_AUTH_SECRET, RESEND_API_KEY, AUTH_EMAIL, EMAIL_ASSET_URL, AUTUMN_SECRET_KEY, OPENROUTER_API_KEY

Optionally add AUTH_E2E_TEST_SECRET for E2E tests on previews.

7. Enable branch builds

Enable non-production branch builds for preview deployments. Push a branch and Workers Builds creates a preview deployment with a stable per-branch URL.

</details>

<details> <summary>Vercel setup</summary>

Connect your repo to Vercel. Set the required Vercel and Convex preview variables listed in the environment variable matrix below.

Vercel: Project Settings > Environment Variables
Convex: Project settings > Default Environment Variables > Add with ✓ Production

Push a branch and Vercel creates a preview deployment with its own Convex preview backend.

</details>

Convex cleans up preview deployments after 5 days (14 days on Professional). If you hit DeploymentQuotaReached anyway (team quota is 40, counted across all projects), the deploy script can self-heal by pruning the oldest eligible preview — opt in by setting CONVEX_MANAGEMENT_TOKEN and CONVEX_PROJECT_ID (see the env matrix).

Production Deployment

Set the required platform and Convex production variables listed in the environment variable matrix below.

Platform: Project Settings > Environment Variables (CF Workers or Vercel)
Convex: Select your Prod deployment > Settings > Environment Variables > Add

Deploy

Push to your production branch (default: main) and the connected platform deploys automatically, or trigger a manual deploy:

Cloudflare Workers:

bunx wrangler deploy

Vercel:

vercel --prod

<details> <summary>Self-hosted production with Coolify</summary>

Use the existing Cloudflare Workers or Vercel setup for preview deployments, and run production on Coolify when you want a self-hosted Node app with the same Convex cloud backend.

Architecture:

Previews: Cloudflare Workers or Vercel, using the existing preview deploy flow above
Production app hosting: Coolify
Backend/data/auth: Convex cloud production deployment

Coolify setup:

Add the repo as an application in Coolify and use the Nixpacks build pack
Set the build command to:

bunx varlock run -- bun scripts/deploy.ts

Set the start command to:

node build

4. Set app-level environment variables in Coolify: - NODE_ADAPTER=1 - CONVEX_DEPLOY_KEY - TOLGEE_API_KEY (optional) - CONVEX_INTERNAL_URL (optional, only if the app container can reach Convex through a private Docker network URL) 5. Set the required Convex production environment variables in the Convex dashboard 6. Set SITE_URL on the Convex production deployment to your public production domain

The build command intentionally reuses scripts/deploy.ts so production stays aligned with the existing deploy flow: Tolgee sync remains optional, Convex is deployed during the build, and PUBLIC_CONVEX_URL / PUBLIC_CONVEX_SITE_URL are computed automatically from the deploy output instead of being copied into Coolify by hand.

</details>

Quick Start

Four commands to a running app with a local Convex backend and seeded admin:

gh repo create my-saas-product --template stickerdaniel/saas-starter --clone
cd my-saas-product
bun install
bun run dev

Visit http://localhost:5173 and sign in:

admin@local.dev

LocalDevAdmin123!

No external services required. To activate optional features (email, OAuth, billing, AI), add keys to .env.convex.local. See the environment variable matrix below.

<details> <summary>What about the Convex cloud dev deployment?</summary>

I'd recommend the local embedded backend for day-to-day work. Each git worktree gets its own isolated Convex instance, you can develop multiple features in parallel without conflicts.

bunx convex init                              # creates a Convex project

convex init prints a CONVEX_DEPLOYMENT value — add it to .env.local. bun run dev still uses the local embedded backend; the variable is only needed for dev:cloud and the Convex CLI.

bun run dev:cloud                             # frontend + cloud Convex backend
bunx convex env set KEY value                 # set backend env vars (see .env-convex.schema / env matrix below)

</details>

User Settings

Users can update their profile, change their password with live strength feedback, swap their email (triggers re-verification), manage passkeys, and review or revoke active sessions. Uploaded avatars and attachments are validated on the server and cleaned up automatically.

Type-Safe Environment Variables

varlock validates env vars against two schemas and generates TypeScript types from them. .env.schema covers SvelteKit (Vite), .env-convex.schema covers the Convex backend. If a required variable is missing or mistyped, you find out before the app starts.