InKCre

Appearance

Getting Started ​

InKCre helps you bring information scattered across your tools into an info-base you can return to and use. Start here to understand the experience, then choose how you will access an instance. You do not need to be an InKCre developer to begin.

What is InKCre? ​

InKCre collects information into an info-base, can organize information already there when that improves later use, and makes it available for retrieval and other tools. Think of the info-base as reusable product memory built from Blocks and Relations, rather than only a folder of copies.

For example, you might collect articles from RSS feeds, keep track of saved GitHub repositories, and capture messages you forward to a Telegram bot. Later, you can find an article from a phrase you remember, follow its related information, or make it available to a trusted assistant.

Collection, Organization, and Application are connected capabilities, not mandatory stages. A collector may preserve source relationships without performing Organization, and you can retrieve information without first configuring an AI provider. Extensions add integrations with different sources and tools; each has its own setup and limits.

Why use it? ​

Saving information is useful only if you can find and reuse it. An article in one app, a repository in another, and a note in a third can become difficult to bring together when you need them.

InKCre gives that information a common home without making its usefulness depend on the original collector or a single client. You choose the sources that matter, then access the info-base from the Web app, the command line, or connected tools in your workflow. Self-hosting also lets you choose where the instance runs and where its information is stored.

Start with a concrete need—such as finding useful articles from your subscriptions—rather than connecting every source at once. One working source and a successful search are a better first milestone than a large collection you cannot yet use.

How do I start? ​

1. Choose how to access an instance ​

An instance stores your info-base and runs capabilities such as collection. A client, such as the Web app, connects to that instance. Opening the Web app does not create an instance for you.

This guide assumes one user-owned deployment. InKCre is not a hosted sign-up service or a multi-user account system; keep its instance authority on devices and tools you trust.

2. Collect one useful source ​

Choose your first source; a public RSS feed is an easy starting point. Each source guide covers its own prerequisites, Extension setup, and first collection. Once you can retrieve a known item, add personal sources one at a time, with the credentials and permissions each requires.

3. Find what you collected ​

Follow Find What You Saved to maintain the search index, search for something you remember, and open a result. Finding a real item completes the linear Getting Started path, independently of your deployment choice.

Model-assisted Organization and semantic retrieval are optional next steps with their own provider and maintenance setup. InKCre does not automatically configure a daily digest or Telegram/email push notifications: making information available in your tools is distinct from proactively sending it.

Your next step ​

If you do not have an instance yet, open Self-Hosted and choose a deployment path. After the first-use path works, continue with the User Guide's formal chapters for more sources, collection schedules, Organization and retrieval maintenance, and browsing or connecting applications to your information. You can also return to Self-Hosted for deployment operations and customization. If you want to understand or contribute to the implementation, use the Developer Guide instead. For the project's values and direction, read About InKCre.