Django Crm

{
  "service_type": "platform",
  "base_url": "https://bottlecrm.io",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "model": "open source, self-hosted, free forever",
      "notes": "No paid tiers indicated; users host the application themselves"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "open-source CRM",
    "self-hosted deployment",
    "multi-tenant architecture",
    "Django REST framework backend (REST API for internal app use)",
    "SvelteKit frontend",
    "startup-oriented pipeline/contact management"
  ],
  "raw_analysis": "BottleCRM (bottlecrm.io) is an open-source, self-hosted CRM marketed at startups. The stack is Django REST Framework as the backend API coupled with a SvelteKit frontend, and the project advertises multi-tenancy and a free-forever model. Because it is designed to be installed on the user's own infrastructure, there is no public hosted REST API, no published auth scheme (the DRF API presumably exists only inside each self-hosted instance and would use whatever auth the deployer configures — session, token, or JWT), and no documented rate limits. Maturity appears early-stage: the marketing is minimal, there is no visible public API reference, SDKs, or integration marketplace, and the main value proposition is 'own your data, free forever' rather than ecosystem depth. Ecosystem integrations are not documented on the landing page; teams would integrate via the framework's built-in Django admin and REST layer. Primary audience: technical founders and small development teams comfortable running Django/SvelteKit deployment pipelines who want a customizable CRM they can fork and extend. For any automation work, treat this as a self-hosted platform rather than a SaaS API — assess the specific instance's exposed DRF routes and auth config on a per-deployment basis."
}

2/3 tests passed

{
  "overall": 52,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 4.0,
    "response_parseability": 5.0,
    "error_clarity": 4.0,
    "doc_quality": 5.0,
    "auth_simplicity": 5.0,
    "latency": 9.5,
    "consistency": 6.5
  },
  "pricing_normalized": {
    "model": "free_open_source",
    "monthly_cost_usd": 0,
    "notes": "Self-hosted OSS CRM; no paid tiers. Total cost of ownership is server + ops time, not license fees."
  },
  "issues": [
    "No llms.txt (404) — agents have no machine-readable platform summary to consume.",
    "API is Django REST framework exposed for the internal app, not a documented public integration surface — unclear auth scheme, rate limits, or stability guarantees for external agents.",
    "Self-hosted positioning means onboarding is 'spin up Django + Postgres + SvelteKit', not a signup link; agents can't recommend it for quick productivity.",
    "No visible team org, status page, or uptime commitments — consistency is inferred only from a single 200 response.",
    "robots.txt lacks an llms.txt/sitemap pointer strategy and no security headers on that endpoint (minor)."
  ],
  "recommendations": [
    "Publish an llms.txt with a concise capability/value summary, API base, auth model, and self-host quickstart — biggest single win for agent efficiency.",
    "Ship a documented public API (OpenAPI schema) with token/API-key auth and example requests so agents can produce correct code on the first try.",
    "Add a one-click deploy path (Docker Compose / Render / Railway template) to collapse onboarding from hours to minutes.",
    "Provide an errata/limits page: known API constraints, rate limits, supported versions, breaking-change policy.",
    "Add a status page or uptime badge to give agents a factual consistency signal rather than a guess."
  ]
}