Installation
PatentFlow consists of the application (API), a PostgreSQL database, the web app for the firm, the disclosure form for clients and - optionally - a language model. We take care of installation, configuration and updates; the application runs with Docker on a Linux server in your environment or ours, and the web app and the form are static files. Your firm sets up nothing on the server.
Steps
- We install PatentFlow on the server and create your firm's first administrator.
- The administrator sets a password with "Forgot password" and invites the other users in the web app.
- Mail server, web app address, EPO access data and AI providers are set in the web app under Settings.
Demo mode
Everyone can switch the web app to example data with "Demo mode" in the sidebar – a fictitious firm with clients, files, AI drafts, deadlines, planning, office mail and invoices – to find their way around or try things out. The example data lives in a database of its own; the firm's files stay untouched. In demo mode no AI runs, no e-mail is sent and the firm's settings can't be changed. Administrators reset the demo with current dates; on request it is switched off.
With or without AI
AI is optional in every form – a local language model is not required either. We set up one of three variants with you; API, database and web app run on their own in each of them:
- With a local model (default): the model runs in a container on the same server, natively on the host, or on a separate server in the firm's network – for instance a GPU server for shorter response times. It only accepts requests carrying the configured key.
- Without a local model: no language model is installed. AI functions run only with the providers administrators connect in the web app – such as Claude or an own OpenAI-compatible server – and only for clients that allow the model. Without an explicit choice for the application, the client or as the firm default, no external model is used.
- Without any AI: the light edition without any language model. Files, docket, planning, office mail, letters, fees and invoices work as usual, and every AI control is hidden.
Setting up the interfaces
The accesses to the offices and the mailbox belong to the firm. They are entered under Settings → Interfaces, stored encrypted on your server and never sent back to the browser. All interfaces are optional; without them PatentFlow works with uploads and manual entries.
- EPO Open Patent Services (OPS) – free of charge. Create an account at developers.epo.org (introduction: epo.org) and an app; the EPO reviews the registration first. Enter the consumer key and secret and check with "Test connection". OPS serves the import of foreign rights, monitoring and the register comparison of European filings.
- EPO account for MyEPO and Online Filing – created at ciam.epo.org/registration. It is required for the EPO mailbox and for Online Filing 2.0.
- EPO mailbox (MyEPO) and Online Filing 2.0 – for both interfaces the production client credentials (client ID and secret) for the “Machine to Machine Service API” (MyEPO) and the “OLF2.0 Machine to Machine Service API” have to be requested by e-mail from
[email protected]. Then the MyEPO administrator grants mailbox access and the Online Filing administrator adds the B2B account with the “Draft” right for EP1001. You enter client ID and secret under Settings → Interfaces. The EPO mailbox fetches the EPO's communications, Online Filing 2.0 takes EP applications as drafts; signing and sending happen there. - DPMAconnectPlus – for the register comparison of German filings. The firm concludes a contract with the DPMA (standard contract and description on the DPMA's "DPMAconnect" page; one-time connection fee of €200, the queries are free). Enter the DPMA user name and password. The DPMA supplies register data and publications, not office communications.
- Mailbox for office mail (IMAP) – a mailbox of its own, or a folder, to which the firm forwards the offices' mails. With a filter on sender or subject PatentFlow fetches only matching unread mails and takes their PDF attachments. For most providers server, user and password are enough.
- Microsoft 365 no longer accepts a password for IMAP. The firm registers an app in Entra ID, grants the application permission
IMAP.AccessAsApp(Office 365 Exchange Online) with administrator consent and creates a client secret. In the Exchange Online PowerShell it registers the app (New-ServicePrincipal -AppId <application ID> -ObjectId <object ID of the enterprise application>) and gives it access to the mailbox (Add-MailboxPermission -Identity <mailbox> -User <object ID> -AccessRights FullAccess). In PatentFlow choose "Microsoft 365 (OAuth)" and enter directory ID, application ID, secret and the mailbox address; serveroutlook.office365.com, port 993. - Importing e-mails by hand needs no setup: e-mails (.eml, from Outlook .msg) are dragged into a file or onto the office mail page.