Document pipelines for technical teams
An active workspace instead of a folder of scripts. Documents arrive, get converted, named, filed and routed by rule on our servers, and one search covers Repora and every connected drive.
Feature availability is confirmed during access planning.
You could write this. That is the problem.
A watcher on a folder, a converter, a naming convention, a copy step, a retry, and somewhere a credential that expires. It works until the person who wrote it is busy, and then it is an operational dependency nobody wants to own. Repora is the same pipeline expressed as a rule you can read, running on our servers, with the result of every run recorded.
Rules instead of a scheduled job
A rule reacts to an incoming document or runs on a schedule: name it, convert it, file it in a shared space, send it out for review. Jobs execute on Repora’s servers rather than on a machine you maintain, and the activity view records what each run did, so a failed step is visible instead of silent.
Run commands in natural language
Describe the document you want or the step you want taken in plain language, rather than composing a query or a filter by hand. It sits on the same workspace as the rules, so what you ask for and what a rule does act on the same documents and the same permissions.
Connected drives, one search, one permission model
Connect Google Drive and OneDrive folders and search across them and Repora together, by name, type, owner or date. Access is controlled per shared space rather than per copy, so the boundary a rule operates inside is the same boundary a person sees.
What runs today, and what we are not offering
Runs today: shared spaces with access control, version history, built-in viewers, search across Repora, server-side conversions, and rules that name, convert, file and route an incoming document on a trigger or a schedule.
Availability to confirm: rule controls for editing, pausing and re-running a rule and inspecting the recorded result, the full set of trigger conditions, background processing after the browser closes, connected Google Drive and OneDrive folders, and natural-language search.
Not offering: there is no published API reference, no SDK and no way to provision yourself an account and script against it today. Repora holds no SOC 2 report and no ISO 27001 certification. Tell us what you need to integrate with and we will tell you plainly whether it exists yet.
Bring the script you are tired of maintaining
Tell us what your team needs to store, find or review. We will discuss access and confirm the details relevant to your workflow.
- Describe the trigger, the transformation and the destination
- We map it onto rules and show you the recorded run
- Where a condition is not supported yet, we say so
