> For the complete documentation index, see [llms.txt](https://grouple.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://grouple.gitbook.io/docs/overview/introduction.md).

# Introduction

### What is Grouple?

Grouple (grouple.pro) is a reverse-auction marketplace for group bookings. Customers submit a single enquiry, receive competing proposal bids from multiple venues, compare them side by side, and confirm their booking — all in one place.

Venues and merchants use Grouple to receive qualified leads, manage enquiries, generate AI-assisted proposals using Amazon Bedrock (Claude), maintain a digital sales library for proposal generation, track lead and booking analytics, manage property listings, and settle commissions.

### Who Uses Grouple?

<table><thead><tr><th width="165.6456298828125">User Type</th><th>Description</th></tr></thead><tbody><tr><td><strong>Customers</strong></td><td>Event planners or individuals looking to book a venue for a group event</td></tr><tr><td><strong>Merchants</strong></td><td>Venue owners or managers who list venues and respond to enquiries</td></tr></tbody></table>

### Core Platform Flow

```
Customer submits enquiry
        ↓
Grouple matches & broadcasts to relevant venues (DB trigger)
        ↓
Venues receive lead notification (Edge Function → Email)
        ↓
Merchant views RFQ and generates AI proposal (Bedrock Claude 4.6)
        ↓
Proposal sent to customer (Edge Function → Email)
        ↓
Customer compares proposals and confirms one
        ↓
Settlement auto-synced (DB trigger → commission_settlements)
        ↓
Confirmation emails sent to both parties (Edge Function)
```

### Core Platform Flow <a href="#tech-stack" id="tech-stack"></a>

<table data-header-hidden="false" data-header-sticky><thead><tr><th width="190.12969970703125">Layer</th><th>Technology</th></tr></thead><tbody><tr><td>Frontend</td><td>React + TypeScript (Vite) hosted on AWS Amplify</td></tr><tr><td>Backend API</td><td>Node.js on AWS ECS + EC2 (Auto Scaling)</td></tr><tr><td>Database</td><td>Supabase (PostgreSQL)</td></tr><tr><td>Auth</td><td>Supabase Auth (GoTrue / JWT)</td></tr><tr><td>Email</td><td>Supabase Edge Functions</td></tr><tr><td>AI Proposals</td><td>Amazon Bedrock (Claude 4.6)</td></tr><tr><td>PDF Extraction</td><td>Node.js Worker + Amazon Bedrock Claude 4.6</td></tr><tr><td>CDN / DNS</td><td>AWS CloudFront + Route 53</td></tr><tr><td>Container Registry</td><td>AWS ECR</td></tr><tr><td>Secrets</td><td>AWS Secrets Manager</td></tr><tr><td>Observability</td><td>CloudWatch + X-Ray</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://grouple.gitbook.io/docs/overview/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.