The full-stack platform tuned for AI agents.
Install one CLI and one skill, and your coding agent gets a whole cloud backend: hosting on a live URL, databases, serverless functions, file storage, a code sandbox, CPU and GPU jobs, hosted models, media services (image, speech, sound, music, video), workflows, and a quick model call with gipity ask. Templates give it a running start; kits drop in the hard parts (multiplayer, vision, payments, push notifications) with no server setup. No API keys to wire for the built-in services. Works with Claude Code, Codex, Grok, or opencode, and it's always your code.
This is the capability map. New here? Start with getting-started.
Everything below is driven by the gipity CLI from your coding agent, and the same REST API backs the Monitor web app.
Build and host apps
Start from a template or a complete app with gipity add <name>, edit files locally (they sync), and gipity deploy dev to a live URL at dev.gipity.ai; gipity deploy prod ships to app.gipity.ai. Custom domains get automatic certificates. gipity page inspect and gipity page screenshot check the deployed page in a real browser.
Load web-app-basics for front-end practice, deploy for the pipeline, app-debugging for verifying a page.
Functions and databases
Serverless JavaScript functions in functions/, called at /api/<PROJECT_GUID>/fn/<name>, with permissions declared in gipity.yaml. A PostgreSQL database per project, schema in migrations/, applied on deploy. Tests in tests/ run with gipity test against the deployed functions.
Load app-development, app-database and app-testing.
Records
Declare tables with field metadata in gipity.yaml and get validated REST CRUD, provenance and an audit trail, plus an auto-generated UI.
Load app-records.
Services your app calls - no API keys
LLM, image generation and editing, video, text-to-speech, sound effects, music, transcription, location and web push, all first-party. Your app's users can pay from their own credits (user_pays, the default) or you pay (owner_pays).
Load app-llm, app-image, app-video, app-tts, app-audio, app-location or app-notify.
Users, payments, uploads, realtime
Sign in with Gipity (app-auth), charge your users through Stripe (app-payments), presigned uploads up to 30 GB (app-files), and multiplayer rooms with shared state (app-realtime).
Sandbox
gipity sandbox run executes JavaScript, Python or Bash in an isolated container with ffmpeg, ImageMagick, pandas, LibreOffice and 60+ other tools. No network inside; fetch inputs first.
Load sandbox-tools for the full list.
Jobs
Long-running CPU and GPU work (gipity job), billed per second, with logs, retries and completion hooks.
Load jobs.
Workflows
Pipelines triggered by a schedule, a webhook, a record change or by hand, authored as workflows/*.yaml. Deterministic steps (function, record, notify, condition, timer, approval, sub-workflow) cost nothing; llm steps call a model with only the tools they declare (db_query, records, web_search, web_fetch, http, memory). A heartbeat is a scheduled workflow with one llm step: gipity workflow create --heartbeat.
Load workflow.
Generate media while you build
gipity generate image|video|speech|sound|music writes the file straight into your project.
Ask a model
gipity ask is one model call: a question, optional files or images, optional JSON schema. No chat history, no tools.
Files and recovery
Every save keeps a version. gipity file versions, gipity file restore and gipity file rollback undo a file or a whole tree.
Load version-history.
A deployed app sends from gipity@gipity.ai with the email() service or a workflow notify step; gipity email test and gipity email log check the send path.
Load email.
Credits and billing
Gipity runs on credits (1 credit = $0.001). Model calls, media generation, sandbox and jobs spend them; storage and databases are metered daily. Running out stops paid calls only; it never takes a site, data or app offline. gipity credits shows the balance and plan limits, gipity credits buy opens checkout, and Monitor's Plan tab does both.
Load plans.
Monitor
The Gipity web app: every project with its URLs and deploy state, traffic, errors, compute runs with output and logs, test runs, files with version restore, spend, billing, alerts, secrets and API tokens.
Where to Start
- New account: getting-started.
- Building an app:
gipity add web-simple(front end) orgipity add web-fullstack(front end, functions and a database), then web-app-basics or app-development. - A game: 2d-game or 3d-world.