Hack A Ton

$ hack_a_ton.init() — ok

June 5–7, 2026//Black Sea Coast

We're building AI agents.On the beach.In a weekend.

48 hours. 50 hackers. Real problems from real companies. Bring a laptop and a caffeine tolerance, leave with something that works.

48h on the coastReal production problemsFirst client validated
online
_
// hack-a-ton.runtime//agents.deploy(beach)//50 hackers · 1 weekend//jun 5–7, 2026 · black-sea.coast//powered by ambasada//ton (ro.) ≈ tuna//
// hack-a-ton.runtime//agents.deploy(beach)//50 hackers · 1 weekend//jun 5–7, 2026 · black-sea.coast//powered by ambasada//ton (ro.) ≈ tuna//
// brand.runtime --live

HACK·A·TON

*ton (ro.) ≈ tuna · we still don't serve seafood

goal=ship_real_thingswindow=48hcoords=44.1n_28.6eedition=2026.06
50
// hackers picked
3
// days of build by the sea
€4,500+
// cash prizes
7+
// sponsors & mentors
// open innovation · ai agents

It's not a slide-deck hackathon. It's a weekend of real build.

Sponsors bring concrete problems from their companies — real, boring stuff that deserves to be solved. You and your team pick a topic, take your room by the sea, and build until Sunday night.

If your topic came from a sponsor, your team can keep building with that sponsor as your first client. Meaning you walk out with a product, a client, and a validated problem.

Not a course. Not a summit. A place where things get built.

// 01

Real problems, not toys.

Sponsors put production problems on the table. You solve one.

// 02

On the coast, not an open-space.

Rooms by the sea, meals on the terrace, BBQ on the beach Saturday night.

// 03

Leave with a client, not just a trophy.

Top teams keep going with the sponsor.

// who

Who is Hack A Ton for?

developer.role

Developers

Backend, frontend, full-stack, AI/ML. If you ship code and know what an LLM API is, this is for you.

founder.role

Founders & makers

Built something before, or about to start? This is the perfect weekend to test an idea in the open.

student.role

Students

If you contribute on GitHub, run side-projects, or just want to learn by building — you're welcome.

// selection By application. No CV needed — the section that matters is «what you've worked on / what you've built».

Solo? We'll help you find a team on arrival. max=5 / team.

// format

3 days. 3 simple rules. 1 demo at the end.

day_1.mdmodified01/03
Friday June 5

Day 1

Kickoff · Topics · Teams

  • 14:00Arrival & coastal check-in
  • 16:30Sponsors pitch their topics (5–7 min/sponsor)
  • 17:30Team matchmaking + team formation
  • 18:30Technical brief + rules + rubric
  • 19:00Dinner & networking

PS
Want to start hacking at 22:00 with a coffee on the terrace? Go for it.

day_2.mdmodified02/03
Saturday June 6

Day 2

Build day · Mentoring

  • 09:00Standup + announcements
  • 09:00–13:00Build + 30-min mentor slots
  • 14:00–17:00Build + 1:1s with sponsors
  • 17:00Mid-checkpoint (5min/team)
  • 18:00Dinner on the beach (BBQ, weather permitting)
  • 20:00–02:00Night hacking. Mentor on-call until 23:00.
day_3.mdmodified03/03
Sunday June 7

Day 3

Demo Day · Judging · Prizes

  • 09:00–12:00Final push (code freeze 12:00)
  • 13:00–15:30Demo Day (pitch 5min + Q&A 3min)
  • 16:00Winners announced + prizes
  • 17:00Closing cocktail
01

Output

Live demo + pitch in Problem / Solution / Demo format. No slides without a demo.

02

Stack

Any language, any stack. You can start from existing (open-source) code as long as you call it out.

03

Topic

Pick from the sponsors' list or freestyle (Open Innovation track).

// what you walk out with

It's not about the trophy. It's the position.

We're still locking down the final logistics with partners (logistics, prizes, credits). What's on this list is what we're sure you walk out with.

// 01

Real production problems

Sponsors put concrete problems on the table. Pick one. Build a real solution, not a demo for the sake of it.

// 02

Top mentors

Founders, CTOs, and AI specialists who bring production experience, not Medium articles.

// 03

Open Innovation track

Don't like any sponsor topic? Build whatever you want, judged on the same rubric.

// 04

Demo Day exposure

Pitch in front of founders, sponsors, hiring managers. The room you want to be in for what comes next.

// 05

Welcome kit + tee

Event tee, badge, stickers, sponsor merch. Honest swag, not landfill.

the cool part
// 06

First client validated

Pick a sponsor's topic and ship — and you keep working together after the hackathon.

// sponsors

Building together with

RareCloud
Assista AI
Chronic AI
Okapi
Cult of Coders
+ your spot here+ your spot here+ your spot here
// who judges you

Mentors & Judges

Announced weekly on LinkedIn / IG. Expect familiar faces from the Romanian tech ecosystem — founders, CTOs, senior engineers, investors.

??
Founder · TBD
TBA

announced soon

??
CTO · TBD
TBA

announced soon

??
AI Engineer · TBD
TBA

announced soon

??
Founder · TBD
TBA

announced soon

??
Senior Engineer · TBD
TBA

announced soon

??
Investor · TBD
TBA

announced soon

A good fit as mentor?Email us →
// faq

Frequently asked

  • Application is free. We're currently negotiating final logistics with partners (stay, meals, transport from Bucharest) — confirmed details will be sent to selected participants before May 18. Hack A Ton itself doesn't charge a participation fee.

  • Email us at office@ambasada.pro with who you are, what you've worked on (link a repo, project, or describe it), what you're into, and whether you're coming with a team or solo. Applications close May 18 — or when we hit 80 apps. We confirm within 5 days. (We'll move to a proper form once it's ready.)

  • You don't need to be an expert. Mentors help with AI-specific parts. You do need to ship code in a modern stack (Python, JS/TS, or another relevant language) and have built something before (a project, internship, public repo).

  • Yes, totally fine. Friday evening we run matchmaking — you connect with other hackers based on skills and interests. Most teams form on the spot.

  • Yes, max 5 people per team. If your team is already set, mention it in your application and have each member apply separately (everyone needs to be selected).

  • No. Hack A Ton is on-site. It's part of the experience — networking, in-person mentoring, dinner on the beach. If you can't make it to the coast, see you next edition.

  • The code stays with your team. Sponsors don't claim exclusive rights. If you pick a sponsor's topic and want to keep going post-event, that's negotiated separately as a normal services contract.

  • If you pick a sponsor's topic and your team ships something working, the sponsor can become your first client. That means a post-event pilot contract on terms you negotiate. (Not mandatory — you can also just take the code and go.)

  • We're working with partners on a final prize pool (cash, API credits, cloud) — we'll publish the locked-in list before applications close. If something doesn't appear here, treat it as not yet confirmed.

  • Laptop, charger, your wide-band attention span, swimwear (optional but recommended). The accommodation covers basics.

  • Stay logistics are being finalized with our partners — selected participants will get the full breakdown before the event. If your application doesn't make the 50 spots and you still want to come as an observer, email us.

  • We put you on the waitlist. If someone drops, we call you. Either way, you get Discord access to the community — where things happen year-round.

  • May 18, 2026, 23:59. Or until we hit capacity (80 applications for 50 spots).

More questions? office@ambasada.pro

Applications close May 18, 2026

Time to decide:
ship slides or ship code?

40–50 spots. Selection by application.Applications close May 18.

Takes 5 minutes. Gets you 3 days by the sea and potentially a first client.Not the worst trade.