petal.build valid

Petal Pro Documentation

**v4 migration note:** The AI Admin Chat was rewritten in v4 to use Jido and ReqLLM (replacing the LangChain-based implementation from v3). If you added custom LangChain tools in v3, you'll need to reimplement them as native `Jido.Action` modules described below. The tool surface is the same; only the implementation pattern changed.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T19:38:52.304Z. Cached copy · Source on petal.build

# Petal Pro Documentation
# https://petal.build/petal-pro
# This file contains all Petal Pro documentation concatenated for LLM consumption.
# Individual pages available at /petal-pro/raw/{path}
# Page index available at /petal-pro/docs.json

# What is Petal Pro?
# Source: https://petal.build/petal-pro

# What is Petal Pro?

[Petal Pro](https://petal.build) is a Phoenix boilerplate template with the goal of drastically reducing your time from a new project to a production-ready web application.

We've worked on web applications for over a decade now. PHP, Ruby on Rails, Backbone JS, React, Meteor JS, Ember JS, and now Phoenix. Having built and deployed a number of Phoenix apps into the wild ([Kindly](https://www.kindlyapp.com.au/), [Travel Massive](https://www.travelmassive.com/) and [Talentbookr](https://talentbookr.com.au/)) we realised that the `mix phx.new` generator it produces a very lean web application and leaves a lot of decision-making to the developer.

To the more experienced developer, this can be liberating, however, it's also great to have more of a turnkey solution with a sensible set of defaults that get you fully up and running. A solution that, out of the box provides:

- a component library so you don't have to think too much about the design
- working authentication and user management so users can register and change their settings right away
- admin functionality allowing the basic management of users
- a way of logging user activity so you can see how users use the application
- some email templates that are ready to go and easily editable
- a cheap and reliable email service provider chosen for you (but easily changeable) to send transactional emails
- a CRUD generator that produces a clean and deployable interface
- a way to deploy to production in less than 10 minutes

Having not found the above solution, me and my business partner Nic decided to build it - the result is Petal Pro.

<div class="bg-blue-50 dark:bg-blue-900/20 border-l-4 border-blue-400 rounded-r-lg p-4 my-4 text-blue-900 dark:text-blue-100"><p>ℹ️ <strong>Information:</strong> <strong>Not an Elixir developer?:</strong> Phoenix web apps now compete with Javascript single-page applications thanks to its impressive web socket abilities via LiveView. We hope more Javascript developers will see the immense time-saving abilities of using Phoenix (along with Petal Pro). Imagine having a web application that feels like a SPA, but is all server-side code. You still can create reusable components and don't need to worry about an API. It really can cut your development time in half.</p></div>

## What's included in v4

v4 is the biggest release yet. Here's a summary of what's new on top of the existing foundation:

### GDPR compliance

A "Your Data" settings page (`/app/users/your-data`) lets users download all their personal data as a JSON file and submit account deletion requests. Deletions run as background jobs via Oban, with soft-delete and anonymization cascad
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=petal.build · GET /v1/domain/petal.build · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for petal.build:
1. POST https://agentwebmap.com/v1/sites/petal.build/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://petal.build/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/petal.build/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/petal.build).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.