Application
Next.js and React
App Router pages, server-rendered public surfaces, route handlers, protected flows, and reusable React components.
For Developers
A production-conscious Next.js SaaS foundation for AI RevOps automation.
AgentFlow Enterprise is built for senior developers and technical buyers who want to inspect the stack, understand the boundaries, and decide whether to adopt, license, customize, or acquire the asset.
Stack summary
A pragmatic SaaS stack with the right surfaces already in place.
The codebase centers on Next.js, React, Supabase, Stripe, PayPal readiness, OpenAI, GitHub Sponsors webhooks, Sentry readiness, analytics readiness, and Vercel deployment conventions.
Auth and data
Supabase
Auth, server/client Supabase helpers, storage/data foundation, and tenant-aware documentation for RLS review.
Billing
Stripe and PayPal
Stripe checkout, webhook lifecycle, billing portal route, PayPal checkout readiness, and plan handling without exposing secrets client-side.
AI
OpenAI
Server-side qualification calls with validation boundaries and buyer-safe language around AI-assisted results.
Provider events
Webhooks
Stripe and GitHub Sponsors webhook support with signature-oriented handling and operational docs.
Deployment
Vercel
Deployment-oriented Next.js setup with analytics readiness, Sentry configuration paths, and environment variable documentation.
Architecture highlights
Designed around server-side trust boundaries.
AgentFlow separates public evaluation pages from protected dashboard flows, keeps provider credentials server-side, and documents the implementation state so developers can audit before extending.
- Server-rendered public pages for buyer discovery and low frontend runtime overhead.
- Route handlers for AI qualification, checkout, provider callbacks, health, and webhooks.
- Supabase Auth and server helpers for session-aware protected routes.
- Stripe webhook lifecycle and billing access helpers for subscription state review.
- Public demo route isolated from production lead, CRM, and billing writes.
- Documentation set covering env vars, onboarding, security, billing, integrations, and troubleshooting.
Technical status
Implementation evidence plus honest limitations.
The asset is credible because it is specific about what exists and explicit about what still needs verification.
API and webhook safetyImplementedProvider secrets remain server-side; webhook routes are documented for verification and idempotency review.
Dashboard protectionImplementedProtected dashboard access is handled through `proxy.ts` with additional server-side checks in sensitive routes.
TestsPresentNode test files cover AI qualification, Stripe webhooks, GitHub Sponsors webhooks, and public demo validation.
Revenue validationNot provenThe codebase should be evaluated as a technical asset, not as a proven revenue engine.
Google workflowsReadiness-onlyCalendar and Sheets should remain described as readiness paths until a UI and full end-to-end flow are verified.
Limitations
What a senior technical buyer should not assume.
This is a serious foundation, not a shortcut around production due diligence.
- No claim of paying customers, enterprise adoption, or live revenue proof.
- No SOC 2, ISO 27001, penetration test, SLA, or certification claim.
- Stripe live mode, Sentry staging capture, and first-customer onboarding still need buyer-side verification.
- Google Calendar and Sheets are readiness/configuration paths unless implemented and tested for a target deployment.
- Production data policies, backups, incident response, and support SLAs should be finalized by the adopting operator.
- Any client-specific CRM, Slack, webhook, or scoring logic requires staging QA before launch.
Review the docs
Start with the technical docs, implementation status, API references, and buyer verification checklist.
Run the tests
Use lint, build, and Node tests to confirm baseline behavior before changing provider or dashboard code.
Verify staging
Validate live billing, webhook delivery, auth redirects, and monitoring before inviting real users.
Developer review
Inspect the docs, try the demo, then decide whether the foundation fits.
The goal is not to oversell the asset. It is to make the technical review clear enough that a serious buyer can move quickly.