Product
Product
Stackap has two halves: Cloud, which builds and runs applications and is live in early access, and Business, which runs and grows a service business and is being brought onto the same platform.
Stackap has two halves: Cloud, which builds and runs applications and is live in early access, and Business, which runs and grows a service business and is being brought onto the same platform.
Each page below describes one capability: what it does, how it works, and what it does not do yet. Cloud pages describe what runs today. Business pages describe software that already exists and say plainly what an outside agent can and cannot reach. Nothing is listed here until it is true.
Pages in this section
- Cloud: Stackap Cloud is the build-and-run half of Stackap: git push to HTTPS, Postgres, storage, domains, cron, logs, backups and rollback, operated by your agent.
- Business: Stackap Business connects the lifecycle from lead to booking, job, payment, books and repeat customer in one system an agent can operate. In development.
- CRM: The customer-management part of Stackap Business: clients, leads, deals, quotes and tasks, linked to bookings, payments and books. In development.
- Sales: Quotes with public links, a deal pipeline, and follow-up jobs that chase leads, quotes and overdue payments. Part of Stackap Business. In development.
- Communications: SMS, email, voice, web chat and team messaging in one hub with a shared history per customer, plus an AI voice agent. Part of Stackap Business.
- Scheduling and operations: Bookings with an availability engine, recurring schedules that generate themselves, jobs with checklists and photos, and crew check-in. Stackap Business.
- Finance: A double-entry ledger with period close, bank reconciliation, financial statements and per-job profitability, posted from real payments. Stackap Business.
- Workforce and HR: Team members, applications, onboarding checklists, documents, performance reviews, commissions and payouts for crews and staff. Stackap Business.
- Marketing: Review requests and replies, a local SEO automation engine, SMS and email campaigns with opt-out, and lead attribution. Stackap Business.
- Documents and e-signatures: Create, send and sign documents with native e-signature, generate PDFs and keep files with the customer or worker they belong to. Stackap Business.
- Commerce and payments: Invoices, card checkout, refunds, worker payouts, e-commerce orders, print-on-demand fulfillment and business websites. Part of Stackap Business.
- Automation and agents: The scheduled jobs and in-product AI agent inside Stackap Business, and how approvals, scoped tokens and idempotency are being applied to them.
- Deployments: How Stackap deployments work: a git push is built into a Docker image, health-checked beside the old version, and only then switched live.
- Databases: How Stackap gives each project its own Postgres database and role, a Supabase-compatible data API, a table browser, and what it does not yet offer.
- Storage: How Stackap stores uploaded files in a Cloudflare R2 bucket you own, served by the open-source Supabase storage service, and what is verified so far.
- Domains: How Stackap attaches custom domains: one DNS record you create, a DNS check before issuing a certificate, automatic HTTPS, and expiry monitoring.
- Cron jobs: How Stackap runs scheduled jobs by calling a path on your app, imports vercel.json crons, records every run, and what the schedule semantics are.
- Environment variables: How Stackap stores secrets: AES-256-GCM encryption bound to project and name, values masked when listed, stdin-only input, and how build-time values work.
- Logs: How to read Stackap build logs and live runtime logs from the CLI or API, the size limits and rotation, and what is not collected.
- Monitoring: The checks Stackap runs on itself, how alerts reach Telegram, the per-project load-time metrics, and the blind spot of a monitor on the same machine.
- Backups: How Stackap backs up databases and repositories to a bucket you own, encrypts them, and proves they restore, plus the gaps that remain.
- Rollbacks: A Stackap rollback re-activates the previous deployment with one command, health-checking it first. What it restores, and what it cannot.
- Scaling: How Stackap scales an app by running 1 to 8 copies behind a load balancer on one server, the measured throughput, and what multi-server scaling still lacks.
- Agent-first infrastructure: What agent-operable infrastructure means in practice at Stackap: commands, an HTTP API and plain-text docs an agent can use without a human in the loop.
Stackap is in early access. Tell us what you run and we will reply with a straight answer about whether it fits.
Ask for an invitationLast updated .