Is the high level instruction compiled to a flowchart under the hood? If so maybe a conversational interface is another layer on a flowchart and not an alternative? Overall it makes sense that flowcharts are limiting when they get big, yes. Product looks cool congrats on the launch.
At Coherence, we're building the infrastructure layer that enables customers to make sense of the data in your product using AI agents. Our product enables you to get a chat interface live in your existing application, with access to all your current backend endpoints and APIs, in less than an hour.
We’ve spent the last few months talking to AI-native teams across fintech, health, legal, and other high-stakes domains. A consistent theme came up: while everyone is investing heavily in LLMs — evals, prompt/model tuning, model experimentation — almost no one has a clean way to integrate human review into production workflows.
Most teams are stuck cobbling together brittle systems: Slack alerts when models are uncertain, spreadsheets to track review outcomes and result quality, manual tagging and triage by engineers, business teams waiting on dev cycles to change rules and integrations.
We built Coherence to solve this. It’s a control plane for production AI that brings structured human oversight into your app with just one simple API call. With Coherence, teams can: Route edge cases to the right human reviewer in real-time, let business users own the rules and thresholds with no dev time required, monitor what’s being flagged and how it’s resolved, improve AI behavior over time via structured feedback loops.
If you’re deploying AI where correctness matters — and spreadsheets aren't cutting it — we’d love your thoughts. We're currently looking for more design partners and early users to help us shape a great product!
We've built a data generation studio that creates robust test datasets for testing their LLM applications in just minutes. While working with hundreds of engineering teams on DevOps automation, we discovered a critical gap: everyone wants to build AI products, but acquiring, labelling, and organizing test data for tasks is a massive challenge.
The current approaches to creating "golden datasets" for LLM testing are either infrastructure-heavy (observability-based) or time-consuming (manual creation). Many teams end up relying on intuition-based development, which leaves crucial questions unanswered about model selection, edge cases, and performance optimization.
Our solution generates comprehensive, realistic test datasets tailored to your specific use cases. You provide context (existing examples, domain information, or system prompts), and it creates robust test data that helps you:
- Balance distribution across your test suite including edge cases
- Evaluate prompt effectiveness across various scenarios
- Compare and optimize model selection
- Identify and handle edge cases systematically
- Assess performance across diverse use cases
- Support rapid R&D experimentation with different data shapes
We're launching this as the first data studio focused on giving AI engineers both speed and precision in their development workflow. If you're building AI products, we'd love your feedback on our approach to making LLM testing more reliable and efficient.
Appreciate the POV, and agree that Coolify has a much better community around it! A lot we can learn from. Not sure we agree on the license front since we do allow commercial use.
Coolify and cnc are very different technical solutions. Coolify is a server you deploy to a VM that then can schedule workloads onto that VM, managing features like ingress and updates. cnc is a client-side CLI that schedules workloads into managed cloud services like lambda, cloud run, ECS, or Kubernetes. It orchestrates public cloud provided services instead of providing them itself (e.g. RDS vs. MySQL in a docker container on a VM). The trade-offs here are too big for a comment and both are a great fit for different use cases. We dive in a bit deeper with our POV here: https://www.withcoherence.com/post/the-2024-web-hosting-repo...
At Coherence (withcoherence.com - I'm a cofounder) we are delivering the open-source benefits of Coolify (less vendor lock-in, cheap hosting costs) via our open-source CNC framework (cncframework.com) while still keeping a hosted SaaS control plane that eliminates the "few hours of fiddling with setup" that the blog author minimizes here. Maintenance and configuration complexity over time (as you customize and use click-ops to configure) are endless, especially as you get more usage or host more projects.
Coolify is awesome software, and alongside similar tools like Caprover, Dokku, and Cloud66, it has its role. But for business use-cases I believe that giving up managed cloud services is too big a leap to make sense, and that a middle-ground approach will win in the long term.
Hey HN, Zach here, cofounder of Coherence (withcoherence.com). We’re excited to announce the launch of AWS Lmabda support for our open-source CNC framework. Let us know what we can do to make it better!
Hey HN, Zach here, cofounder of Coherence (withcoherence.com). We’re excited to announce the launch of free-tier compatible serverless deployment options for both AWS and Google Cloud Platform (GCP). This new functionality enables developers to deploy applications directly to AWS Lambda and GCP Cloud Run, leveraging the power of serverless architectures without intermediary platforms. We hope that these provide a way to use Coherence for low-volume or R&D type projects, and open up some interesting new use cases!
Appreciate this feedback, thanks so much for sharing!
The tagline clearly doesn't say what we want here, but the idea is that we are a framework that sits on top of IaC tools like the ones listed above, and makes them easier to use. Under the hood, cnc uses terraform/opentofu to actually manage infra, the cnc layer adds new concepts like environments onto those tools as well as providing a much simpler, higher level configuration with cnc.yml, while still enabling you to edit the templates directly so you're not limited in the infra you can deploy for your app. In this way, we're the first tool of that kind, sort of like a "PaaS in your own cloud" but we expose the plumbing as a CLI.
In the ever-evolving software development landscape, one of the most influential ideas of the past decade has been the "git flow" working style, thanks to the iconic blog post "A Successful Git Branching Model." Here, we suggest an updated workflow with less long-lived branching.
Developer experience is hard to quantify, and is not a simple as correlating with subjective input of "how devs feel." SPACE and DORA are attempts to get objective about engineering productivity. Some teams prefer to use a more subjective approach here as well. There aren't any great answers for equivalents in developer experience, yet.
There are some obvious "tooling" considerations that impact developer experience. For the most part, these are related to how much devs can "self-service" the various parts of the SDLC, and how good the user experience of that service flow is. For teams that want to get a great experience without reinventing the wheel, internal developer platforms like what we're building at Coherence (withcoherence.com) are a great answer.