Partner Docs
Partner PortalGet started
ProgramProgram Standards

Program Standards

The quality control standards the Softr Partners team applies to partner profiles, portfolio entries, demo videos, registered projects and Enterprise applicants.

The following are quality control standards used by the Softr Partners team.

Partner Profiles

  • All data fields completed
  • Well-written short and long bio
  • High-quality profile photo and feature image
  • Current proof of Softr professional certification
  • All profile content must be written in English. The only exception is the long bio, where partners may optionally include a version or description in their local language.

Portfolio Entries

  • App solves a real business problem, for a client and/or internally. Simple vibe-coded applications without a clear business use case are not eligible portfolio entries.
  • All data fields completed
  • Well-written short and long description
  • High-quality feature image and gallery images
  • If the entry is set to “Public”, permission granted from the client to share the project publicly (if applicable)
  • No sensitive user data exposed in images or video (no PII)
  • Optional, but highly recommended: a demo video meeting the demo video standards
  • Local languages are allowed here.
  • App URL: provide the public-facing link (no preview links). It needs to be a Softr app/build.
  • Images: images need to focus on and show the functionality of the Softr app.
  • Demo video: needs to show the functionality of the app. A testimonial clip can be added, but the focus should be on the Softr app itself.
  • Submit in the Partner Portal. A single job can be both a portfolio entry and a submitted project.

Demo Videos

  • Video hosted on a publicly accessible, embeddable URL (Loom, YouTube or Vimeo)
  • High-resolution screen recording of the Softr app with audio narration in English, no camera
  • No sensitive user data exposed in the screen recording (no PII)
  • The video should showcase live app functionality, telling the story of what the app is used for and who uses it
  • The video may also tell the story of the creation of the app: the problem(s) the customer was looking to solve and how the partner addressed them during this project
  • “Behind the scenes” elements such as Softr Studio or underlying data sources/automations may be shown, but are not required
  • 2 minute minimum length, 5 minute maximum length recommended

Registered Projects

  • The project must be for an external client (no internal or personal projects).
  • Project work must be actively happening at the time of registration (support work counts), or the project was completed within the past 12 months and the customer confirms by submitting a final feedback survey.
  • All data fields completed, including customer contact information. Provide the app Studio URL (no preview links).
  • Project updates provided by the partner every 20 work days (monthly) while the project is active (requested automatically).
  • Customer feedback survey sent by the partner from the project details page using the Send survey action, available once the Project end date is set to today or earlier. One survey response per project.
  • Projects need to be written in English only.
  • Submit in the Partner Portal. A single job can be both a portfolio entry and a submitted project.

Enterprise Partners

For the full framework, including what is and isn’t changing, expectations and the application process, see Enterprise Partner Designation.

Quick reference: applicants must meet all of the following.

  • Be a current Softr Premium Partner, or have been a Premium Partner within the last 12 months.
  • Carry active professional liability insurance of at least $1M USD.
  • Have experience working with at least 2 enterprise clients (250+ employees, $250M+ USD annual revenue), and provide a case study and/or reference material for that work.
  • Offer enterprise-level professional services in a clear format: clear pricing and timelines/phases in professional quoting, clear quality control mechanisms and high-quality documentation.
  • Have a team capable of effectively supporting enterprise clients: 4+ people covering Softr development (front-end, backend, business logic, workflows, APIs and custom code), account management (on- and off-boarding, regular check-ins, stakeholder management), change management, internal escalation management, training, ongoing support and legal/IT security counsel (may be external).

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Partner Docs documentation and read it in full, instead of answering from memory.

https://partner-docs.iamno.pro/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://partner-docs.iamno.pro/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.