No-code, AI-coded, pro-code — three ways to build on Turtini

Turtini sits in a corner most platforms don't reach: full-featured no-code modules AND a real developer surface AND a path for AI-generated code, all on one shared data model. Use as much or as little of each corner as you need.

No-code — Builder + Wally + Marketplace
Drag-and-drop sites, runbooks, slide decks, email campaigns. Wally ("Hey Wally…") runs your day-to-day ops via voice or chat — every action is preview-confirmed and reversible for 24h. The Marketplace ships pre-built templates that spin up complete workflows in a click.
• When to use: most operational work, every team that doesn't have a developer
• Where to start: /platform — the breadth view of every module

AI-coded — Pull-to-host + IDE workflow + Wally action cards
Generate your site with Lovable, Bolt, v0, or Cursor. Push it to GitHub. Turtini hosts it at your custom domain — with vulnerability scanning, preview URLs for non-main branches, and a one-click GitHub Action bootstrap if your site needs a build step. AI agents in Cursor / Claude Code / Windsurf read and write your org via the @turtini/mcp server. Wally proposes confirmable action cards inside the app instead of executing blindly.
• When to use: marketing sites, customer-facing apps, anything you'd otherwise build with a no-code site builder
• Where to start: /build — the developer-platform overview

Pro-code — SDK + Public API + MCP + Live dev
A typed Bearer-authenticated REST API at api.turtini.com. The @turtini/sdk npm package wraps fetch with auto-pagination and idempotency. The @turtini/mcp server is a thin protocol wrapper around the same client. Live local dev via the @turtini/cli (turtini-dev serve). OpenAPI 3.1 spec at /v1/openapi.json — generate a client in 50+ languages.
• When to use: data integrations (Salesforce, NetSuite, your warehouse), backend services, internal tools that build on top of Turtini's data model
• Where to start: /build — same page, scroll past the AI-coded section

Why all three on one platform:
Most SaaS platforms force a binary choice: lock yourself into no-code (with vendor walls and limited extensibility) or rebuild from scratch in code (months of infrastructure work). Tools like Lovable and Bolt give you generated code but no platform underneath. Turtini gives you both — start no-code, drop into pro-code at a single team's pace, mix freely. Your data is the same in all three corners; you can switch entry points per workflow without rebuilding anything.

You don't pick one and stay there. Most orgs end up using all three: marketing teams in Builder, finance in the Accounting module's UI, developers wiring an integration through the SDK, and an AI agent in someone's IDE making targeted updates throughout. Turtini's job is to make all of that work on the same source of truth.