yoeven
DefaultModel: Hosting only one model, the best open source model
Open source models are catching up to their closed source counterparts, but inference for them is scattered across general GPU providers. Those providers constantly swap models, and pricing, reliability and support differ from one to the next. You don't get the consistency of a provider like OpenAI.
Large labs get around this by aggregating their own GPU resources, pointing most of the capacity at their latest model, and migrating users there when a new one ships. We want the same for open source models.
So we're taking a different approach. We host one model, the best one, voted by you, the community. We host it for a quarter, and every quarter you vote to keep it or replace it based on the latest releases.
- All GPU capacity goes into one deployment instead of a catalog
- Serving is tuned for that one model, not averaged across fifty
- Performance stays consistent across every request, with no degradation in quality
- When a better model wins the vote, you migrate by changing one model ID instead of rewriting an integration
1. yeah, we've optimized significantly for latency, give the API a try and you'll see it's pretty fast.
2. more than you think, we use a wide range of providers internally depending on the context needed. Exa could be great in some for example people search but is pretty bad at getting the latest content of the page, Parallel is better there. Apify is great for getting google ranked pages. Perplexity is great at financial data which Exa is pretty bad at. Context7 (coming soon) great at code, way better than exa for code. Depending on the use case, different indexes do better. we're also seeing companies with access to prosperity data like Valyu.
Show HN: OpenWebSearch – A router for web search indexes
Hi HN, I'm one of the people behind OpenWebSearch (https://openwebsearch.ai).It's a router for web search indexes. You POST to one endpoint with a `provider` field, and it normalizes both the request and the response for web search indexes like Parallel, Brave, Exa and moreWhy we built it: we run a model company (Interfaze) and a lot of our models are smaller in size and we're experimenting if...
Show HN: A one-click install company brain Chrome extension built ontop of Box
We see two types: workflows & agents.
Workflows are the most common, there's a pipeline like processing loan documents before data gets loaded to the next step or translating user comments before being stored in the database.
Agents are where you have a chat based system or a brain of sorts that calls many tools to achieve a user goal. The model doing this is a lot better at non deterministic task which then delegates to Interfaze for specific deterministic actions like OCR, Web extract then consumes that data. That's the article you referenced :)
Excited to see the results
We're working a lot more on speed in the coming few weeks :) More GPUs and more optimizations.
Our has been focus on quality of output first and we'll make optimizations as we grow :)
The lite models are great for simple use cases but won't don well in more complex OCR use cases.
We serve it though an API. Check out the docs: https://interfaze.ai/docs
It's free to gets started.
The focus has been for deterministic outputs that require high accuracy. In situations where there is "one right answer"
See the full benchmark: https://interfaze.ai/leaderboards
Interfaze is a more powerful version of them combined into a single model, you can run multi turn tasks like extract all the text and object from this document then translate or generate a report.
It's like getting the best of both worlds from pure DNN/CNN models like Paddle and the flexibility and nuace of an LLM while outperforming both in accuracy.
Here's a good example: https://interfaze.ai/docs/audio/speech-to-text#long-audio-tr...
E.g. For an OCR task, the first pass will be handled by the CNN, converted to shared tokens which the transformer can consume, correct any issues if needed and a decoder that can handle both the DNN and transformer output.
You can find the explanation and the comparison in the article, which we benchmarked pure CNN models, pure LLM models and a hybrid architecture like ours.
I'd be happy to test it against your sample and see how we can get good results at a lower per page cost. Feel free to email me [email protected]
However, if we see enough people who has something super niche that our model can't handle, we might start considering a fine tuning service
Code manipulation probably not since it's a lot smaller of a model compared to a Claude Opus which is SOTA for code generation/manipulation.
Generally code generation is a non-deterministic task by nature and general LLMs tend to be better at them.
Interfaze: A new model architecture built for high accuracy at scale
CNNs + VLM outperforms pure VLMs on OCR
Ask HN: What are your thoughts on LLM routing?
Would devs want a single API that automatically routes to the best LLM for their goal while having basic tools built in like web scraping, web search, etc?Or would devs want way more control like a Lang chain/AI SDK, easier to swap models but you basically gotta build the chain yourself.What do you guys thing?
if you find it interesting, you could add it to your articles too as a comparison :)