Convex.dev Reviews

1. Sherry

   2 months ago
   Great DX

   Really great developer experience. Helpful devs in chat.

   🏁 Competitors: Supabase

GitHub Reviews

1. Reinhard

   · Boss at CLOUD Meister · over 5 years ago
   perfect 4 open Source

Convex.dev mentions (15)

• useChat hook in Chef codebase.

  This is the only AI app builder that knows backend. By applying Convex primitives directly to your code generation, your apps are automatically equipped with optimal backend patterns and best practices. Your full-stack apps come with a built-in database, zero config auth, file uploads, real-time UIs, and background workflows. If you want to check out the secret sauce that powers Chef, you can view or download the... - Source: dev.to / 9 months ago

• Monitor websites changes with Firecrawl Observer and Docker

  Convex account with production deployment. - Source: dev.to / 12 months ago

• The Reluctant Founder

  I architected a boring but functional agency management app powered by Convex. But, I encouraged her to get started with a ready-to-use option, SPP.co. - Source: dev.to / over 1 year ago

• Bringing Convex Dashboard into my dev environment

  When I first started using convex, I realized how awesome and easy it was to use the dashboard. It offers an amazing overview of logs, the ability to edit table data, and view your app health. However, as a developer who always has an insane amount of browser tabs open, I found myself constantly switching back and forth just to check on things, and with the massive amount of tabs, I always spent more time looking... - Source: dev.to / over 1 year ago

• I shipped my first iOS app, here’s my experience

  Convex provides a real-time database solution for Daily Reps, allowing me to store and retrieve data in a highly efficient and scalable manner. This enables me to provide users with a seamless experience, even as they engage with the app and perform various actions. This will be especially useful when I start building the web and Android versions. - Source: dev.to / over 1 year ago

GitHub mentions (2472)

• Your Agent's Confidence Score Is Not a Probability

  All of this assumes you can actually inspect what the agent did — the real inputs after resolution, the real tool outputs, the real intermediate steps. That is the other half of the workflow. AgentLens captures the trace: every model and tool step, resolved inputs, raw outputs. agent-eval scores and gates the output; AgentLens gives you the unforgeable, agent-didn't-author trace data for Tier 1+2 to score against... - Source: dev.to / 1 day ago

• Foreman 101: agentic coding as Kubernetes resources

  # git: the API token, plus the credential used for the push Kubectl create secret generic foreman-github \ --from-literal=GITHUB_TOKEN="$GITHUB_TOKEN" -n foreman-system Kubectl create secret generic foreman-git-credentials \ --from-literal=token="$GITHUB_TOKEN" -n foreman-system Helm upgrade foreman llmkube/foreman -n foreman-system --reuse-values \ --set agent.githubToken.secretName=foreman-github \ ... - Source: dev.to / 1 day ago

• Stop Judging Every Run: Eval Sampling Is a Budget Decision, Not a Coverage One

  This is why eval and observability ship as a unit, not as separate purchases. agent-eval scores and gates the output — the tiers above, drift, hallucination. AgentLens captures the trace of how the agent got there: every model step and tool call, the resolved inputs, the raw outputs, the trajectory. Two things fall out of that:. - Source: dev.to / 11 days ago

• Claude Code permission rules: how allow, deny, and ask actually match

  The real fragility is in trying to constrain arguments. The docs are explicit that a pattern like Bash(curl http://github.com/ *) fails to do what it looks like it does. It won't match curl -X GET http://github.com/... (option before the URL), curl https://github.com/... (different protocol), curl -L http://bit.ly/xyz (redirects to GitHub), URL=http://github.com && curl $URL (variable), or curl http://github.com... - Source: dev.to / 13 days ago

• 3 ways to add link previews to a React app (with and without a backend)

  Fallback chains — og:title → twitter:title →

  SSRF protection — if you fetch user-supplied URLs, you MUST block localhost, RFC-1918 ranges, and internal hostnames, or your preview endpoint is a proxy into your own infrastructure

  Caching — you do not want to re-fetch a URL on every render

  Rate limiting — a public...

  - Source: dev.to / 15 days ago