@droplana_com · X

@DropKlient · X

The only website freelancers need to manage their work.

@danielkleach · X

is a branded client portal for files, answers, sign-offs, and signatures. No more scattered email threads, docs in Google Drive, or confusion about who is waiting for whom. Business and client both see what is done and what is in progress on both sides, in

@emironic · X

- free plugin for Claude and Codex to put your work as public website with single line `publish to Revdoku` prompt.

@jitendraballa · X

@baptistedulac · X

time tracking for freelancers and agencies

@HalxDocs · X

Reqit—a fast, local-first API client for developers.

@amiuchat · X

我做了一个桌面工具：Token Switch。 给 Codex / Claude Code / OpenCode 重度用户统一管理 Provider、模型、Token、Base URL、连通测试和消耗统计。 多个 Agent，一个 Token 工作台。欢迎试用，也欢迎吐槽你最烦的配置问题。

@klorityx · X

One workspace for project management, documentation, test management & CRM. Enterprise features without enterprise pricing.

tahazsh · HN

Hi! I’m Taha. In many agentic products that support workflows (including one I worked on), I noticed they either don’t support node-based editors, or use React Flow and go through the difficult work of integrating it into their product to run it and work with their existing logic. So I thought about creating a tool that could help with this by closing the gap between the editor and the runtime. That’s why I created Wayflow. The basic architecture is simple: you just need to create a graph (which is a JSON object) that the runtime knows how to run. The runtime doesn’t care where that graph is coming from, it just needs the right schema. And with the help of the editor, you can create the graph, and then export it or directly save it on your backend in your database. And then when you want to execute it, you just hand it to the runtime. The runtime can either stream the execution (which is useful for the editor), or give you the final result. How you execute the graph is up to you: t

@BMFDigital · X

@X_LetsConnect · X

- all-in-one outreach platform.