Build on INC Platform

Documentation

Reference and tools for the local platform preview.

Start in three steps
  1. Create an account or sign in to your local workspace.
  2. Open a service, create a resource, and try its local workflow.
  3. Create an API key with the required service scope to connect your application.

INC Dev

Organize repositories, define build pipelines, and prepare deployments from one workspace.

Configuration validation is available locally. Builds and deployments require a runner; commands are never executed by this console.

Open INC Dev

INC Data

Create collections, store JSON records, and access them through an authenticated API.

Collections persist in the local PostgreSQL database. Each collection is private to its owner.

Open INC Data

INC AI

Save prompts, configure models, and run an AI playground against your own Ollama server.

Generation uses your local Ollama service. If a model is not installed, the playground reports that instead of inventing a response.

Open INC AI

INC Storage

Create private buckets, upload files, and retrieve them through authenticated downloads.

Files are stored in private S3-compatible buckets. Downloads require the owner’s session or scoped API key.

Open INC Storage

INC Connect

Compose email, SMS, WhatsApp, and OTP messages in a private test outbox.

Local test outbox only. Capturing a message does not send email, SMS, WhatsApp, or an OTP to a real recipient.

Open INC Connect

INC Pay

Create sandbox payment links, test a checkout, and inspect the resulting transaction history.

Sandbox only. No funds are charged, settled, or paid out. Production payments require a licensed provider integration.

Open INC Pay

INC Work

Organize tasks, notes, calendar events, and meeting plans in your workspace.

Tasks, notes, and schedules are saved locally. Meeting records are planning tools; video conferencing and mail delivery need separate services.

Open INC Work

Persistence and access

PostgreSQL stores resources and activity; MinIO stores private bucket objects. Every service resource is owned by one workspace user. API keys are hashed at rest, scoped by service, and expire within 90 days. Docker volumes preserve data across container restarts.

Production infrastructure

The console is a local control-plane preview. Deployment definitions do not execute builds. Messages stay in the test outbox and payments stay in the sandbox. Infrastructure settings list the services and adapters needed to enable real provisioning.