About the challenge

Get your hands dirty with Mastra and Elasticsearch! In this hack night, we'll be building AI agents that can use past context in order to make better decisions.

Get started

Before hacking, please make sure you:

  • Create a DevPost account and hit "Join hackathon" (required for submission)
  • Register for an Openrouter key (Link will be provided on-site)
  • Signup for an Elasticsearch Serverless free trial

Visit the GitHub Repo for further instructions.

 

Requirements

What to Build

Build an AI agent with memory, using Mastra as the agent framework and Elasticsearch as the memory store. Your agent should answer questions it couldn't answer without remembering something: your data, your history, your context.

Start from the starter repo and pick your tier:

Tier 1 - Easy Win: Elasticsearch as long-term memory. Ground a Mastra agent on your own data. Ingest any corpus - games, recipes, docs, products, songs (sample datasets included) - and get an agent that only answers from what's really in the index, with citations, via hybrid keyword + semantic search. No timestamps needed. If you're new to agents, you'll have a working demo in under an hour.

Tier 2 - Advanced: episodic memory with time decay. Add the time dimension. Typed memories retrieved with hybrid recall (ES|QL FORK → FUSE) weighted by DECAY, so recent context outranks stale context and superseded decisions lose to their replacements. The retrieval machinery is built - your job is data with a shift or reversal in it, and the tuning: decay window, fusion weights, the query, the agent's instructions.

Bonus on either tier: use Mastra's built-in memory primitives (semantic recall and working memory) backed by Elasticsearch; a reference agent ships in the Easy Win starter. It counts in the judging rubric under "Use of Mastra," as does retrieval tuning under "Use of Elasticsearch."

Any domain is fair game: personal assistants, team knowledge, ops runbooks, recommendation engines, whatever your data makes interesting. The best demos show a before and after: the same question answered without memory vs. with it.

 

What to Submit

  • Your project on DevPost, before submissions close (8:00 pm sharp - submit early; you can keep hacking after you submit). Include:
    • A project name and a 2-3 sentence description of what your agent remembers and why it matters
    • A link to your code (GitHub repo or fork)
    • Which tier you built (Easy Win / Advanced / both) and what data you used
  • A live presentation: 1-2 minutes, hard cap. The winning format: ask the same question twice, memory-blind vs. memory-aware, with the Mastra Studio trace visible so judges can see the tool calls, the recall, and (if you used them) the memory primitives at work.

Hackathon Sponsors

Prizes

1 non-cash prize
Lego Icons: Bonsai Tree Set
3 winners

Top 3 projects will win!

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

Philipp Krenn

Philipp Krenn
Head of Developer Relations, Elastic

Dan Goosewin

Dan Goosewin
Mastra/Goosewin Media

JD Armada

JD Armada
Developer Advocate, Elastic

Judging Criteria

  • Use of Elasticsearch
    Demonstrates meaningful use of Elasticsearch as a memory store and features such as search, aggregations, and vector search. Tuning the retrieval itself counts here - decay window, fusion strategy/weights, or the ES|QL query (FORK/FUSE/DECAY)
  • Use of Mastra
    Uses Mastra framework to build AI agents and shows agent traces using Mastra Studio. Using Mastra's memory primitives (semantic recall, working memory) with Elasticsearch as the backing store counts here.
  • Creativity
    Presents a unique idea, novel user experience, or interesting technical implementation.
  • Usefulness
    Solves a real problem or provides valuable insights from the data.

Questions? Email the hackathon manager

Tell your friends

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.