Pagerly vs Relay: which is better? (2026)

Relay

Relay.app revolutionizes the way teams approach automation by combining cutting-edge AI capabilities with human-in-the-loop controls.

Relay is an automation platform for teams that want to combine AI-driven workflows with human oversight. It is built for both technical and non-technical users who need to connect apps and automate multi-step processes without writing code. What Relay does Builds automated workflows that combine AI steps with human-in-the-loop approval points Connects with over 100 popular apps to move data and trigger actions across tools Provides an interface designed for use by people without a technical or engineering background Supports the creation of multi-step, sophisticated automations rather than single-action triggers Who uses Relay Relay is aimed at teams that need automation but also want a person to review or approve steps before they complete, rather than fully unattended workflows. It suits both non-technical staff who need to set up processes themselves and technical users who want more control over how automations run across their existing app stack. For makers and small teams, Relay fits into a workflow where automation needs to touch multiple tools while still leaving room for a human check at key decision points, reducing the risk of AI-driven steps running without review. }0shot_prf_lit_qrels_lex-1000-0-omit_0shot_task_qrels-eng-Latn_lit_qrels_lex-100_5058_25199_0-doc_1000_25199_9-fold_0_2_100000_qtype_1_query_id_original.jsonl.txt(1).txt qtype_1_seed_42_num_500_20250912.jsonl (1).txt qtype_2_seed_42_num_500_20250912.jsonl (1).txt qtype_3_seed_42_num_500_20250912.jsonl (1).txt qtype_4_seed_42_num_500_20250912.jsonl (1).txt qtype_5_seed_42_num_500_20250912.jsonl (1).txt qtype_6_seed_42_num_500_20250912.jsonl (1).txt qtype_7_seed_42_num_500_20250912.jsonl (1).txt qtype_8_seed_42_num_500_20250912.jsonl (1).txt qtype_9_seed_42_num_500_20250912.jsonl (1).txt qtype_10_seed_42_num_500_20250912.jsonl (1).txt qtype_11_seed_42_num_500_20250912.jsonl (1).txt qtype_12_seed_42_num_500_20250912.jsonl (1).txt qtype_13_seed_42_num_500_20250912.jsonl (1).txt qtype_14_seed_42_num_500_20250912.jsonl (1).txt qtype_15_seed_42_num_500_20250912.jsonl (1).txt qtype_16_seed_42_num_500_20250912.jsonl (1).txt qtype_17_seed_42_num_500_20250912.jsonl (1).txt qtype_18_seed_42_num_500_20250912.jsonl (1).txt qtype_19_seed_42_num_500_20250912.jsonl (1).txt qtype_20_seed_42_num_500_20250912.jsonl (1).txt I have uploaded several files, each containing multiple records in JSON Lines (JSONL) format, where each individual line represents a valid, self-contained JSON object. Please process all provided files in this format. For every JSON object (i.e., each line) within these files, perform the specific task detailed below, using the data fields found in that line. Query: This is the original search request or question submitted by a user. It represents the specific information need that a search engine or retrieval system must satisfy. Document Text: This is a block of text from a document that has been retrieved as a potential answer or relevant match to the corresponding query. Instruction: Read the provided Document Text and determine how relevant it is to the given Query. Provide a relevance rating for the document based on its content in relation to the query's information needs. Output Format and Storage: For each processed line, the relevance judgment must be assigned as an integer score using the following 4-point scale: 3: Perfectly relevant 2: Highly relevant 1: Somewhat relevant 0: Not relevant The final result for every record must be a new JSON object containing precisely three specific fields: query_id, doc_id, and relevance_rating. Crucially, all of these output records must be saved and provided back to me in one single JSONL file.42 / 42this is what one query and document look like: {