3
8 Comments

Updates: Keyword filtration

🔍 Keyword filtering

You can now filter any source by keywords:

• Include — only receive posts mentioning the topics you care about
• Exclude — mute the subjects you're tired of

Aggregation put everything in one place, but "everything" was still a lot. This is what makes a busy source actually readable. It's quickly become the feature people use most.

✍️ Custom prompts for AI digests

Write your own instructions for how digests are generated — tone, length, format, what to focus on. If our default summary style doesn't match how you read, you can change it instead of living with it.

🔑 Bring your own AI key

Connect your own AI provider and run digests on your model, at your cost, with your own settings. Full control over the output, and no dependence on our defaults.

🌍 Four languages

The full interface and onboarding now work in English, Russian, Turkish and Arabic — including proper right-to-left support.

posted toAvatar for product Aggregaat
Aggregaat
  1. 2

    The keyword filtering feels like the most meaningful update here. Aggregation only helps if people can control the noise, and that seems like a much stronger usability improvement than simply adding more sources.

    1. 1

      you can consider adding more sources when you have small niche , topic or yo ucreate multiple forwarding (you manage multiple channels , and so yo ucreate forwarding rules for each one )

      1. 1

        That’s a good point. Multiple forwarding rules could make the filtering much more useful for niche topics and separate channels. I’ll keep that in mind.

  2. 2

    The keyword filtering feels like the real unlock here. Following ~40 channels and still being able to keep the useful stuff is a much more concrete problem than just “AI digests.”

    With 190 people already using it, this feels like it could be pulling a lot more organic traffic than it probably is right now. That seems especially interesting at this stage where you’re seeing which feature actually keeps people around.

    I’d be curious what happens if that audience gets much bigger.

    1. 1

      Honestly - Half of our users are using the digest , which now supports more then 20 AI providers , for which either we provide API key or you can grab your free API key (all providers have free version)

      We are also curious on how this will scale , but so far so good.

      1. 1

        That 50% digest usage is probably the signal I’d build around. It suggests the AI digest isn’t just a feature — it may be one of the core reasons people get value from Aggregaat.

        I’d be interested in mapping the specific problems around that workflow: filtering noisy sources, AI news digests, following multiple channels, using your own AI provider, etc. There may be some very clear high-intent search gaps there, especially with 20+ providers behind the product.

        That’s the kind of intent research I’d validate before putting more effort into content, because it could show you which part of Aggregaat has the strongest organic acquisition potential.

        1. 1

          Yeah, that’s actually the signal we’re paying the most attention to right now. The fact that ~50% of users are using digests makes us think it’s more than just an additional feature — it may be one of the main reasons people stick with Aggregaat.

          What’s interesting is that the use cases seem to overlap quite a bit: filtering noisy channels, getting AI-powered summaries, following a lot of sources without checking them individually, and now choosing your own AI provider.

          We’re still trying to understand which of these is the strongest underlying problem rather than assuming it’s simply “AI digests.” The 20+ providers are more of an enabler for us at this point.

          Definitely curious to see whether that usage pattern holds as we grow the user base.