Fits the stack you already run.
No connector-count theater. This is what ships today, by category. Where something is unverified or on the roadmap, it says so.
Nothing below is a plug-in you install. Each card ends with the ask, in a builder's words.
Sign in with the directory you already have.
SSO is a platform setting for your organization, not a build step. Your identity provider says who a person is; platform groups say what they can do.
SAML and Auth0
Point the platform at your SAML identity provider or your Auth0 tenant. Access ends where you end it today.
Staff sign in through the company SAML app; the finance directory group lands in the approvers group.
Google and Firebase
For users outside your directory — a partner portal, a public intake app — Google and Firebase sign-in sit alongside SAML.
Vendors sign in to the onboarding portal with Google; our staff stay on SAML.
Zapier, Make, n8n — or any HTTP endpoint.
Workflows are async activity chains, wired to your app's actions with create-workflow and wire-workflow-to-action. One activity is an HTTP POST with templated headers and body — all a webhook consumer needs.
Zapier, Make, n8n
A workflow step posts the record to your webhook and your existing automations take over. Nothing on our side needs to know what runs downstream.
When an inspection is marked failed, POST it to our Make webhook so a ticket gets opened.
Any HTTP endpoint
Same activity, your URL. Headers and body are templated from the record's fields, so your API receives exactly the shape it expects.
On approval, send {{amount}} and {{vendor_id}} to our payments API as JSON with an auth header.
Workflow activities run asynchronously, and we do not claim delivery, retry or exactly-once guarantees — ours or the far end's. Make the receiver idempotent, as you would with any webhook, and log on your side whatever you need to reconcile.
Real tables, a documented API, two named connectors.
Salesforce sync
The platform ships a Salesforce integration endpoint family: sync platform objects with the Salesforce records you point them at, so a deal-specific app works from the accounts your sales team already maintains. Direction, field mapping and refresh are configured per app — confirm the shape with us before you build on it.
Sync accounts and opportunities from Salesforce into crm_accounts and crm_deals; Salesforce stays the source of truth.
RDS lookups
Query-builder lookups keep reference data — price lists, part numbers, customer master — in the relational database it already lives in. The database has to be reachable from our infrastructure; if it sits on a private network, front it with a gateway you control first, the same rule as the workflow HTTP activity.
The order form's SKU field looks up parts and prices from our RDS product table.
Documented REST API, real Postgres tables
Every object is a real table; adding a dimension runs a real ALTER TABLE. The REST API is documented with Swagger, so your systems read, write and dispatch under the same authentication and permissions as the app.
Show me the API call our BI job should use to pull last month's inspections.
PDFs out, files in, short links for both.
PDF generation
A workflow activity renders a PDF from a template and the record's data — an inspection report on completion, a signed approval, a quote.
Generate a PDF report when the inspection is completed, with the photos and the signature.
File storage with signed URLs
Photos, signatures and attachments live on managed cloud storage that is closed to the public — a direct storage URL returns 403. Access runs through time-limited signed URLs: each link is issued per request and stops working when it expires.
Add a photo field to the site-visit form; store originals, show thumbnails in the grid.
Short links
The platform issues short URLs for a public form, a report, anything with a long address you would rather hand over short.
Give me a short link to the public intake form for the printed flyer.
Email and push today. SMS: not verified — ask us.
Email notifications
A workflow activity sends email with subject and body templated from the record's fields — {{field}} placeholders, filled at run time.
Email the requester when status changes to Approved, and copy their manager.
Push notifications
A notification activity pushes to the mobile renderer, so a field technician sees the new work item on their phone.
Push a notification to the assigned technician whenever a job is assigned to them.
SMS
SMS appears in the platform's notification family but is not verified for this release, so we do not list it as shipped. Ask us; we will confirm before you build on it.
Bring the agent you already pay for.
The desktop app connects your agent to the platform over MCP — stdio for clients that spawn a local server, HTTP+SSE for clients on the network. The monster is not picky about who feeds it.
Claude Code
Spawns the MCP server locally over stdio. The guide comes from a live test: config block, first calls, what 401, 403 and Tenant context required mean.
Run whoami, then list-tenants, then use the Acme tenant.
Claude Desktop, Cursor, ChatGPT
Guides exist for Claude Desktop, Cursor and ChatGPT; each is marked live only after we run it end to end ourselves.
Any MCP client
If your agent speaks MCP and can send an Authorization header, it can build here. Same approximately 100 operations, same authorization, same transactions on either transport.
Connect over HTTP+SSE with the URL and token the desktop app shows.
Vite and React by default. Any static build works.
Platform apps render in the web and mobile renderer with nothing to integrate. Your own frontend ships through the same develop → staging → production chain.
Vite + React by default — or any framework that builds to static
An ordinary repository you hold, calling the platform API for public object reads. Install command, build command and output directory are configurable per app; the pipeline ships static output only — a folder with an index.html. There is no SSR and no server runtime today; server-side code is on the roadmap as custom backend functions, not shipped.
Scaffold a React dashboard over the ops_tickets object and deploy it to develop.
Header and body script hooks
Per-solution header and body script slots put your analytics tag, chat widget or consent banner into the rendered platform UI, next to your brand color and logo.
Add our analytics snippet to the header of the customer portal.
- Custom backend functions — on the roadmap, not shipped. Read the roadmap
- Custom domains — not offered yet. Every environment gets an HTTPS URL on our domain.
- SMS — unverified, as above. Ask before you build on it.
- App-store publishing — apps run in the web and mobile renderer; we do not claim native app-store builds.
Something your stack depends on is missing? Tell us — integration and partner requests go to the people who would build them.
Three the IT approver asks first.
Can a workflow call my internal API?
Yes. A workflow's external-service activity sends an HTTP POST, with templated headers and body, to any endpoint reachable from our infrastructure — managed cloud infrastructure we operate, built primarily on AWS. If the API lives on a private network, expose it through a gateway you control first; the workflow does not tunnel in.
Can I bring my own identity provider?
Yes. Users sign in through SAML or Auth0; Google and Firebase sign-in are supported too. Your directory decides who a person is; platform groups decide what they can do.
Do integrations cost extra? Are they metered?
No and no. Integrations are part of the platform, and nothing on the platform is metered — workflow runs, generated documents and notifications are covered by the organization license. No tokens. No credits. No meter. You bring the AI subscription you already pay for. The only other bills are ones you already pay: your AI provider, and whatever the far side of an integration charges on its own plan.
The rest of the approver's list — architecture, data and tenancy, governance and audit, and where compliance actually stands — is on the security hub, with the IT brief as the short version. What the organization license covers, and what it does not, is on pricing.
Bring us something you want built.
CodeMonster is invite only while we work directly with early adopters. Request an invite and we will meet, scope what you want to build, and get you productive. You bring the AI subscription you already pay for.