Langfuse and LangSmith, and Deedglass
Traces show what the agent said. Deedglass's check shows what Postgres did.
The short answer
When to choose Langfuse or LangSmith
When Deedglass fits
- Your agent writes to Postgres, and a trace that says '1 row updated' isn't enough: triggers and cascades can change hundreds.
- You need writes decided before they run, and a record someone else can check offline.
Side by side
| Question | Langfuse or LangSmith | Deedglass |
|---|---|---|
| Shows each step of an agent run | Yes: traces12 | Each tool call it governs |
| Evaluations | Yes12 | No |
| Decides before the call | Not described on their pricing pages (checked 13 October 2026)1 | Yes: rules decide each tool call |
| Checks what Postgres committed | Not described on their pricing pages (checked 13 October 2026)1 | Yes: reads Postgres's change log |
| Signed record of each action, checkable offline | Not described on their pricing pages (checked 13 October 2026)2 | Yes |
| Self-host | Langfuse: free to self-host1 | Yes: free |
| Price (checked 13 October 2026) | Free tiers; paid plans on their pricing pages12 | Free self-host · Pro $49 a month |
Use them together
Keep your traces. Deedglass's record of each write carries the action's id, so a trace step and the check of what Postgres committed can be read side by side.
What Deedglass doesn't do
- It doesn't trace prompts or model calls, and it doesn't run evaluations.
- It sees only the tool calls you put behind it.
Sources
- 1Langfuse pricing · langfuse.com · checked 13 October 2026
- 2LangSmith pricing · langchain.com · checked 13 October 2026
Last checked 13 October 2026. We re-check these pages every month. If something is out of date, write to hello@deedglass.com.
Try it on your own setup
npx deedglass scanGrades only your own setup. Nothing is uploaded.