Pory is an AI portal builder: describe who a portal is for and what each person needs, and it generates a branded portal with its own database, user logins, permissions, forms, approvals, and status tracking. No code required. No repo to babysit either.

What is a client or member portal?

A secure, branded website where the people you work with — clients, members, tenants, applicants, staff — sign in to submit requests, track their status, and find what's theirs. It replaces the spreadsheet, the shared drive, and the email thread currently doing that job badly.

Can Pory power a directory, resource library, or events page?

Yes. Pory generates what your portal needs to share — a searchable directory, a resource library, an events calendar, a job board, and more — each scoped by role, so people only ever see what's theirs.

Can Pory manage applications and reviews?

Yes. Application intake, reviewer scoring, stages, and decisions are one of the workflows Pory generates, alongside directories, resources, and events. Each applicant and reviewer sees only what they should. “When do I hear back?” becomes a status page, not your inbox.

Does Pory still require Airtable?

No. Pory now includes its own datasource, so there's nothing external to sync or pay for. Legacy Airtable-connected portals keep running at airtable.pory.io, untouched.

Does Pory charge per user?

No, never. Pory uses flat pricing with unlimited end users, so a portal with 4,000 users costs exactly what one with 40 costs. Growth is the point; it shouldn't be a billing event.

Do the people I invite need training or account setup?

No. People sign in to their portal with a secure magic link — nothing to install, nothing to learn, no password to forget by Thursday.

How much does Pory cost?

Pory starts free. Paid plans start at $99/month (billed annually) for one portal with unlimited users. All plans are flat-priced — Pory never charges per user, per client, or per applicant.

Can Pory run portals for my own team too?

Yes. The same platform runs portals for staff — leave requests, onboarding checklists, IT and facilities requests — alongside portals for clients and members. Each person gets a secure view of only their own work, and you get to stop CC'ing everyone on everything.

AI Portal Builder for Clients, Members and Teams

Collect

Stop collecting things by email.

Every form, sign-up and upload lands as a record in the same database — attached to the right person, not a thread you forward or a folder you dig through.

Forms

Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

Public pages

An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.

Self sign-up

People create their own account and land in the role you chose for them.

File attachments

Upload and view files on the record they belong to — not in a folder named FINAL v2.

Decide

Decide together, on the record.

Your team works the same records: assign them, score them, approve them with a reason. The person waiting sees where it stands on their own page — without a “quick question”.

Approve / reject with a reason

Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.

Status tracker

“Where's my request?” answered as a progress bar on the submitter's own page.

Board by status

Cards in columns. Drag a record to move it along.

Checklists

Task lists ticked off per record, in its detail view, with progress — onboarding runs, inspections, opening duties.

Assign to a person

Name who a record is for and it lands on their list, and nobody else's.

Notes & scores

A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.

Reminders by date

Renewals, expiries and overdue work, in an in-app inbox and by email.

Control

Same portal. A different view for every role.

One database underneath. Staff, reviewers and members each see their own records and can only do what their role allows — generated from your description, not configured by hand.

Who sees which records

Each person sees their own records, the ones assigned to them, their team's or the ones they manage. Fields can be hidden per role. Generated from your description, not set up field by field.

Passwordless sign-in

A sign-in link by email, by default. Password sign-in if you'd rather.

Your brand

Your domain, your colours, your logo. Members see you.

Generate portals that take the back-and-forth off your plate.

Still running things on a Franken-stack?