> For the complete documentation index, see [llms.txt](https://ample-2.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://ample-2.gitbook.io/docs/start-here/readme.md).
# What is Ample
**Your money, amplified.**
A savings account pays you interest a few cents at a time. Nobody feels excited about it, talks about it, or saves more because of it.
Enter, **Prize-Linked Savings with Ample**
Ample puts the same yield to better use. Every deposit in every Ample vault earns yield in institutional-grade onchain markets, and all of it flows into **one shared pool.** Once a week the pool pays out, sending hundreds of payouts across the pool, topped by a Grand Prize, in amounts that actually make everyone excited about winning.
Your deposit never funds anyone's payout. It stays in the vault, in your name, withdrawable any minute of any day. Win or not, your balance is untouched, and your odds improve the longer you save.
{% hint style="success" icon="water-arrow-up" %}
**Your savings are linked with prizes. You do not lose your principle, yet still have a shot at winning something outsized.**
{% endhint %}
### Proven Idea
This model has a name, prize-linked savings, and it is one of the most successful savings mechanisms ever deployed. The UK has run it nationally since 1956. More than twenty million people hold over £100 billion in it, choosing the chance of a real win over a guaranteed trickle, decade after decade.
What it never had was rails that could take it global, yield you can program. A dollar/asset that works the same in every country. A draw whose fairness is a mathematical fact rather than a promise. Being onchain provides all three, and that is why Ample can offer one pool to every saver on the planet, with results anyone can verify. The full story is in [Research](/docs/research/why-ample.md).
### The longer you save, the luckier you get
Ample is built around a simple conviction, that a savings product should get better the longer you use it. Hold through full cycles and your ticket weight rises. Deposit something every week and it rises again. Go a stretch without winning and the system compounds your odds until you do. A consistent saver carries up to **1.91x** the draw weight of a newcomer with the same balance, and every part of that multiplier is published math you can check. See [Your Odds, Over Time](/docs/how-payouts-work/odds.md).
### On Deposits
Deposits sit in non-custodial audited smart contracts audited built on Euler and Morpho, lending infrastructure that has passed more than twenty independent audits and secures billions across DeFi. Yield comes from institutional-grade, overcollateralized markets under a strict policy of no leverage and no directional bets, **ever**. And every weekly draw publishes a cryptographic proof you can check yourself. The model is documented in [Security & Risk](/docs/security-and-risk/overview.md).
### Where to go next
| You want to | Go to |
| ------------------------------------ | -------------------------------------------------------------- |
| Get the full picture in five minutes | [Understanding Ample](/docs/start-here/understanding-ample.md) |
| See one full week, start to finish | [A Week on Ample](/docs/start-here/a-week-on-ample.md) |
| Deposit now | [Make Your First Deposit](/docs/start-here/first-deposit.md) |
| Check the odds math | [Tickets](/docs/how-payouts-work/tickets.md) |
Ample is built and operated by Layer3 XYZ, Inc.
---
# 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:
```
GET https://ample-2.gitbook.io/docs/start-here/readme.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.