Uruky search engine (paid service)

General
21

Questions for this service - may be on the site but asking here for visibility.

  1. I’ll assume you won’t be open sourcing your server side code. However for client side portion of the site, do you plan on open sourcing that?
  2. Given this is paid, are APIs for paying customers first class?
22

No worries, but those are answered in the FAQ, yes:

  1. This is an “old-school” server-side-rendered app. The server-side code is eventually open sourced (accounts that pay 12 months can download the currently available source code at the time, licensed with BUSL → AGPLv3 after 2 years).
  2. I don’t understand what you mean, could you elaborate? Everyone gets the same service and (generous) rate limits. APIs are included.

Thanks!

1 Like
23

First class API is just an API well documented for use with developers, instead of say scraping the site and reversing building a search request. But you answered my question!

As for this being a server side rendered app, much respect on that decision. React is overdone for simple sites.

And your licensing arrangement is very fair. Good balance of offering server code to users who dedicate as a paying customer.

1 Like
24

I’m one of those 250 :smile: I’ve been using for around 2 months and I’m really loving it. The only thing i’m lacking is lenses from Kagi. I have to manually enter site:… OR site:… , but last I tried it didn’t work that well even with Serper. I had to go to Ecosia and there it worked perfectly. I didn’t test it out that well, ill have to take another look.

Also, pleasantly surprised with how good EUSP index is. Finds me almost everything that I am looking for.

1 Like
25

Thank you for your support!

To be fair, it’s probably one of the most commonly requested features, so I think we’ll eventually have to build it, I was just hoping we wouldn’t have to add that complexity to the UI (both in search and settings).

In any case, `query site:X` was improved for single `site:` bits, multiple were not properly considered and passed on to the API requests to become additive (with or without the OR). I’ve just shipped a fix for that. On that note, Serper, EUSP, Linkup, Mojeek, and Uruky Site Search support this natively (so they should work for your queries perfectly now), the other providers rely on post-filtering.

3 Likes