Data Management
Every process needs data. Customer names, emails, documents, and more. Procly gives you a powerful, secure way to store, access, and control the data that flows through your processes, without building custom databases or writing plumbing code.
The goal of Procly is to allow you to focus only on your business logic and workflows, and let Procly handle things like data management, security, compliance, and more for you.
The Spreadsheet Mental Model
Think of your data in Procly like an advanced spreadsheet. Each Task is a row, and each row has Fields, which are like columns in a spreadsheet, that hold the data for that Task. But unlike a typical spreadsheet, Fields can hold rich, complex data: files, structured objects, lists, encrypted secrets, and more.
Controlled Access at Every Level
Data security in Procly is a foundational part of the platform. Every Stage in your process is given explicit permission to read or write specific Fields of a Task. A Stage sees only what it needs and nothing more. This means:
- Least-privilege by default — A compliance Stage can see certifications and insurance documents but not pricing terms. A procurement Stage can see company information and pricing but not tax IDs. You define what each Stage can access, and Procly enforces it.
- Safe external access — External users (customers, vendors, partners) can interact with your process—filling out forms, uploading files, viewing statuses—without ever seeing or accessing your underlying data. They touch only the Fields you expose, through the interface you control.
- AI containment — AI agents running inside a Stage are held to the same strict data boundaries. They can only read and update the Fields explicitly granted to that Stage. No roaming access, no accidental exfiltration, no surprises.
- Full audit trail — Every read and write to every Field is logged. You can see exactly who (or what) accessed or changed a piece of data, when, and why. Rewind to any point in time for debugging or compliance.
- Egress control/tracking — You can control which external services or endpoints a Stage can access. This is useful for cases where you want to prevent a Stage from accessing certain external services, or you want to limit and track the data that can be exfiltrated from a Stage.
Field Types
Procly Fields go beyond simple text and numbers. You can define Fields that hold files, dates, structured JSON, encrypted secrets, references to other Tasks, and more. Each Field type comes with built-in validation, so bad data is caught early and your process stays clean.
Fields are somewhat similar to Stages in that they can have a public UI for an external user to input data of that type, and validates the data before it can be stored. For example, a Field that holds a file can have a public UI for an external user to upload a file. They also have an internal UI for displaying the data that was collected or generated by the Stage.
Data Across Processes
When a Task moves between processes (for example, from intake to onboarding to fulfillment), its data travels with it. But each process defines its own Field access rules independently. Moving a Task to a new process doesn't grant the new processes Stages automatic access to all of the Task's data.
This makes cross-team handoffs clean and secure. The intake team sees intake data. The fulfillment team sees fulfillment data. Sensitive fields stay locked to the teams that need them.
No Database Required
You don't need to provision databases, write migrations, manage schemas, or worry about backups. Procly handles all of that for you. Define your Fields, set your access rules, and focus on building the process that delivers value to your business. Your data is stored securely, replicated, backed up, and available whenever your process needs it.