Papyrs
Tap a star to rate
What it is
Papyrs is a drag-and-drop builder for company intranets, team wikis, knowledge bases and portals, made so that non-technical staff can create the pages themselves. Its comparison page describes it as "a modern take on wikis/intranets" that was designed "as an intranet site builder from the start". The home page pitches it to teams that want one central place for documents, communication, forms and collaboration without waiting on IT, and says it needs nothing to install or maintain because it is fully hosted. The home page says the current version is completely new but the company has been around since 2011, and it calls itself privately held and "not going away", and it treats support as a core job: all team members, including the founders, work on customer support, so replies come from people who build the product.
What you build and how
Pages and widgets. Papyrs uses a drag-and-drop page editor with a widget library. You add widgets to a page for polls, embeds, checklists, forms, videos, tables, files, calendars and photos, alongside rich text, image galleries and file attachments. For power users, the editor adds Markdown mode, keyboard shortcuts and a command palette. The result reads like a web page rather than a document, and the same editor builds an intranet home, a wiki article, a visual dashboard and a portal section. The company says it uses Papyrs itself for internal project work and for its public knowledge base and blog.
Knowledge base and search. Wikis and knowledge bases live in one place, with find-as-you-type search that looks through pages, comments, files (documents and PDFs), user profiles and form submissions. Template pages can be created once and cloned whenever a new page of that kind is needed. The home page names the employee portal as a core use: pages with training videos, a people directory and onboarding guides for new staff. One customer quoted on the home page says that before Papyrs someone always had to be available to answer questions, and that new crew members now only have to check the intranet.
Project collaboration and communication. Teams work on projects through shared pages where they post and discuss roadmaps, task lists, calendars, code snippets, files and discussions. For internal communication the home page describes a "social intranet" with discussions, internal blog posts, social media mentions and polls, and the comparison page adds an activity stream, a people directory and social media widgets for Instagram, Facebook and Twitter.
Forms and databases. Papyrs includes custom online forms and databases. You build a form directly on a page, collect responses as records, and view and filter those records "any way you want". The comparison page says you can create reports from form data and use form workflows to process requests such as expense reimbursements, and the home page frames the range as everything "from feedback to HR workflows". This is the piece that turns an intranet into a small internal tool for requests and approvals.
Client portals. Papyrs also works as an extranet. You can "Share sections with external people to offer a secure client/community portal", so a consultancy or agency can give clients their own area next to the internal one.
Integrations. Staff sign in with Workspace (G Suite), Slack or Office 365/Teams. Zapier connects Papyrs "to hundreds of services", and the API lets developers build their own integrations and automate workflows. Content from dozens of third-party services can be embedded on pages directly from the editor, and the comparison page highlights attaching or embedding Google Drive documents (Docs, Sheets, Slides, PDFs and so on) and Google Calendars directly on pages, so a Google Workspace company can surface its existing files inside the intranet.
Structure, permissions and branding. Papyrs scales from a tiny team that throws everything into one space to companies with thousands of employees, with as many internal subsites as you need, split by team, department or topic. Permissions are described as straightforward: you run the intranet open or closed and decide who can view and who can edit. Version history lets you compare and roll back any version. Theming covers colors, banner images and logos so the intranet matches company branding, and notification summaries keep people up to date without interrupting their work. The home page lists automatic mobile apps for iOS and Android under "All batteries included".
The evidence from the pages
Papyrs offers a free 14-day trial, risk free, with templates and examples to start from. The home page links to plans and pricing rather than quoting prices on the page itself, and promises no "contact us for a sales pitch": you sign up and start the same day. One customer, a payroll team leader at RCI Subway, calls it "reasonably priced".
For larger deployments the home page lists SSO (like SAML), 2FA and audit logs, under the heading "Enterprise-ready". On privacy, the company calls itself "security nerds and privacy purists", says there is no cookie banner on its site because it does not track visitors, and states that it speaks GDPR and that security is its top priority. On hosting, it takes care of cloud hosting, uptime and backups, and says it is proud of its availability track record.
Customer evidence on the home page includes a five-star average rating in marketplaces like the Workspace Marketplace and Capterra, and named testimonials from customers such as Centric Digital's president and the RCI Subway payroll team. Their common points are ease of use, no programming knowledge required, and responsive support.
Who it suits and who it does not
Papyrs fits small and mid-sized organizations that want a self-service intranet without IT overhead: HR teams running onboarding, operations teams collecting requests through forms, project teams sharing roadmaps and files, and agencies that want a client portal next to their internal wiki. Because forms feed filterable databases and workflows, an ops team can replace a few spreadsheets and email threads with one place, and the Zapier and API options let it connect to the rest of its stack.
It is less suited to anyone who wants a public marketing website, since Papyrs is built as an intranet site builder rather than a general website builder. Its permission model is deliberately simple, open or closed, viewers and editors, which keeps setup fast but may feel light to a large organization with many overlapping access rules. And a team that only needs task tracking will use a small part of what Papyrs offers.