Try DI Cloud without an account

The public mode works without an account and without giving any details. You ask a question in the field above, and the answer comes from the same engine that runs the full version of DI Cloud. The number of messages in one session is limited, because the conversation belongs to nothing and there is nowhere to keep its context.

The difference between a trial and working with an account comes down to memory. Once signed in, a conversation belongs to a project: you can attach files to it, come back a week later and see what an earlier decision was based on. Here, every page refresh starts from nothing.

Whatever you type in the public mode is used only to prepare the answer. It does not become training material for DI Cloud models. If you want to test the tool on your own document, do it after creating an account — the file will then stay with the project instead of a conversation that disappears.

Without an account, the page offers exactly one thing to try: a chat field. You can pick one of four ready-made questions or write your own, up to fifteen hundred characters, since anything longer is trimmed before it is sent. Enter submits the message, Shift with Enter starts a new line. The reply arrives as one finished block rather than word by word, and its length is capped in advance. The exchange does hold some context: every new question travels together with the six most recent messages, so a follow-up about what was just said works, while earlier turns fall out of view. The language of the reply follows the language edition of the page you are reading, and there are ten of them, not the language the question was typed in.

Two limits apply, and they work independently. The visible one sits in the interface: a single sitting covers five messages, after which the input area is replaced by a panel linking to registration and to the plans. The second one sits on the server: twenty requests a day per network address, counted across every tab and window, private browsing included, because the counter belongs to the address rather than to the browser. People working on one office connection therefore draw on a shared pool. Above both of them there is a daily ceiling for the whole service and a separate ceiling on requests within a minute; the latter closes nothing and only asks for a retry. When the counter itself is unreachable, the mode that works without signing in declines to answer at all, which is deliberate: a request that cannot be counted cannot be capped.

What the server keeps from such a session is a shortened hash of the network address and the request counters, and nothing beyond that: neither the questions nor the answers go into any table, so there is no way to reach them from another device. The conversation itself lives only in the memory of the open tab, because with no account there is nothing to attach it to. That is also where what you can try without an account ends. There are no file attachments here, no image generation, no projects and no history, and no confidence marker or list of sources appears beneath an answer. One fixed model setting serves the whole session, so DI Core starts choosing a working profile only once an account in DI Cloud exists.