Open Saas

{
  "service_type": "platform",
  "base_url": "https://opensaas.sh",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "note": "Open source SaaS boilerplate starter kit, 100% free to use, modify, and distribute. Not a hosted service."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Open-source SaaS boilerplate/starter kit",
    "Authentication (email, Google, GitHub, Slack, Microsoft)",
    "Email sending",
    "Background jobs",
    "Landing page/marketing site template",
    "Payments integration (Stripe, Polar.sh)",
    "Admin dashboard",
    "AI example app",
    "Built on Wasp framework (React + Node.js + Prisma)",
    "Shadcn UI components",
    "Self-hostable / self-deployable codebase"
  ],
  "raw_analysis": "Open SaaS (opensaas.sh) is not a hosted platform with a public REST API. It is an open-source, free SaaS boilerplate/starter kit for building SaaS applications using the Wasp framework (React on the frontend, Node.js + Prisma on the backend). The product is a code template developers clone and extend, so there is no service API to integrate against. The site itself is a marketing/documentation page built with Wasp (note the /waspara/wasp/event analytics proxy and __WASP_SSR_DATA__ SSR fallback). \n\nMaturity: The project is community-driven, hosted on GitHub, and has reasonable traction in the JS/React SaaS-starter niche. It is mature enough to include production-oriented features (auth with multiple OAuth providers, Stripe and Polar.sh payments, background jobs, transactional email, an admin dashboard, and an AI example app). \n\nAudience: Indie developers, solo founders, and small teams who want to skip boilerplate wiring (auth, billing, emails) when launching a SaaS product. \n\nIntegrations: Integrations are library/SDK-level within the generated app (Stripe, Polar.sh, Google/GitHub/Slack/Microsoft OAuth, email providers), not API endpoints exposed by opensaas.sh itself. Any 'integration' with Open SaaS happens by vendoring/forking its source code, not via HTTP API calls. \n\nAuth model: None for the site itself; auth is something you configure inside your derived app. No public API keys, no service endpoints, no rate limits to document."
}

3/3 tests passed

{
  "overall": 68,
  "dimensions": {
    "token_efficiency": 7.5,
    "first_try_success": 6.5,
    "response_parseability": 6.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 6.0,
    "latency": 9.0,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "model": "free_open_source",
    "notes": "No monetary cost. Total cost = developer time to fork, configure, and deploy. Not a hosted service, so no usage-based pricing."
  },
  "issues": [
    "Not a hosted API platform — agents cannot 'call' it; it is a codebase to clone and self-deploy.",
    "llms.txt returned HTML (the marketing homepage) instead of a proper machine-readable llms.txt file, which is misleading to agents and crawlers.",
    "No security headers detected on responses, which is a poor signal for a project whose value prop includes authentication and payments.",
    "High friction for autonomous onboarding: no signup-to-productive path; requires Git clone, env config, a database, and OAuth/Stripe key provisioning.",
    "Recommendation is inherently a 'developer project' rather than an 'agent tool', limiting direct agent-driven usage.",
    "Documentation quality and structure not verifiable from these checks alone — only landing page HTML was fetched."
  ],
  "recommendations": [
    "If recommending to users, frame as 'open-source SaaS starter kit for developers' rather than an agent-consumable API.",
    "Publish a real, text-based llms.txt with concise architecture, feature list, and setup steps to improve agent parsing.",
    "Add security headers (CSP, HSTS, X-Content-Type-Options) to signal production-readiness and build trust.",
    "Provide a machine-readable manifest (e.g., JSON listing env vars, required services, and deploy targets) to cut first-try setup failures.",
    "Consider a hosted demo or one-click deploy (Vercel/Railway/Fly) to reduce onboarding time from hours to minutes.",
    "Surface a status page or CI badges in docs to strengthen reliability perception."
  ]
}