A clear brief for every editor.
Assign AI editors to sources, each with its own charter. Define what matters and what belongs in your channels.
A little editorial magic
Kribli. Krabli. Boom!
Krabli helps select the posts that fit your channels. Review and approve in one Telegram backstage, then publish on your terms.
Your sources. Your brief. Your final say.
Good things deserve a careful pair of claws.
The magic, explained
A clear path from the sources you follow to the posts you choose to publish.
Messages arrive from the channels you choose. A starting point for your editorial process.
Your preferences guide the filtering and selection. Fewer repeats. More relevant developments.
Review in your Telegram backstage. The approval/publication action releases posts to your public channels.
Your judgment, put to work
Tell Krabli what belongs. It helps reduce repeated sorting, while keeping an eye on what actually changed.
“Keep official transport updates that affect local journeys.”
An official transport notice fits your brief. Bring it to backstage for your editorial decision.
An example of the intended workflow, not a live AI result or a product screenshot.
Small claws. Thoughtful work.
Source-level attention, a broader editorial view, and your decisions to guide what comes next.
Choose how much help you needAssign AI editors to sources, each with its own charter. Define what matters and what belongs in your channels.
Keep context across developing stories, so familiar topics can still bring meaningful new information.
An editor-in-chief brings a broader understanding of the main topics and ideas across your sources.
Publishing, dropping a post, and marking a topic off-topic offer different feedback. Dropping one item needn’t mean rejecting its whole topic.
A thoughtful backstage. A wider audience.
For example, bring Spanish-language sources into one English backstage. Start with your main public channel in English, then add a Russian edition for a new audience. Your editorial selection and approval stay in that same backstage.
YOUR SOURCE CHANNELS
Your chosen sources · Spanish
Editorial selection
Review & decisions
Approve & publishOne backstage per customer. Release happens here.PUBLIC LANGUAGE EDITIONS
Grow your editions. Keep one backstage.
Publishing automation is adjustable. Approved publication is released through backstage.
Video translation & subtitles
One Transcribe action processes every video attached to a source post, with translated subtitles burned into the picture in your backstage language. When you Publish, each public channel gets videos subtitled in its own language.
For example: Spanish source videos, English backstage review, an English main channel and a Russian public edition.
Click Transcribe on a post with video files. All of its attached videos are processed together.
Translated subtitles are embedded in each video using your preferred backstage language.
The same Publish action delivers video versions with subtitles burned in using each public channel’s language, including new editions you add.
Two Spanish videos arrive in one source message. Transcribe prepares both with English subtitles for backstage review. Publish sends English-subtitled versions to your main public channel and Russian-subtitled versions to your Russian edition.
Illustrative frames and example languages. Add language editions while keeping one backstage and one editorial process.
As much help as you need
For a solo channel operator, a small editorial team, or a publisher reaching several language communities.
Just for you? Keep a private information feed with no public publishing.
Gather source messages into backstage unchanged, with no AI processing. Publish onward only if you want to.
Add optional AI filtering and deduplication, guided by your preferences, to help surface the posts that fit.
Use AI editors and an editor-in-chief for selection with story context, shaped by your editorial decisions.
A few useful answers
Yes. Krabli can gather messages from your chosen sources into backstage without processing them. AI filtering, deduplication, and editorial assistance are optional.
Yes. Use backstage as a private information feed for yourself or your team. Publishing to public channels is optional.
Yes. Start with your public channel, then add umbrella editions in other languages as your audience grows. Editorial selection and approval stay in one backstage. When you Publish, video versions receive burned-in subtitles using each public channel’s language.
Each customer has exactly one backstage channel for incoming content, editorial review and approval. Public channels and their language settings are destinations for that shared process. Several public channels can share the same language.
A Transcribe button appears when a source message has video attachments. Clicking it processes every video file attached to that message and burns translated subtitles into the videos in your preferred backstage language.
Each public edition receives the videos with subtitles burned in using its own language. For example, review Spanish source videos with English subtitles in backstage, then publish English-subtitled versions to your main channel and Russian-subtitled versions to a Russian edition. Adding an edition keeps the same shared editorial workflow.
Your publish, drop, and off-topic decisions help shape future selections. Dropping a relevant post is different from marking its whole topic off-topic. Feedback informs future choices; one action does not guarantee an immediate change.
Yes. Publishing automation is adjustable to your workflow. Backstage remains the release point for approved publication to your public channels.
Let’s find the good stuff
Bring your sources and your idea of what matters.
Krabli can help with the picking.
