About
Built because a spreadsheet stopped being enough
Every team's data starts in a spreadsheet. It holds up right until a second person opens it. Then you're mailing versions around, a column needs to point at another sheet, someone pastes over a formula, and nobody can say what changed. SWAMP is what you move to at that point.
It's a collaborative database. You import a spreadsheet and get real structure back: tables that link to each other, columns with types, totals that keep themselves current. You look at the same records as a grid, a board, a calendar, or a form. You share them with your team at the role you pick, or with the public behind a link.
Underneath it runs on Postgres, which matters more than it sounds. The permission rules live in the database, not in the app in front of it. The thing that decides whether you can see a row is the same thing that stores it, so there is no gap between the two for a bug to slip through.
Who built this
Lohith Kumar Neerukonda
Founder & CTO of Ekoham
I'm Lohith. I built SWAMP after watching the same spreadsheet come apart on team after team: five people typing at once, no history when something went wrong, a share link that gave away more than it should. I wanted the Airtable idea, a spreadsheet that's really a database, without the parts that lock you in. So I put it on Postgres, built it in the open, and I'm still building. If you try it and something breaks, I'm the person who reads the email.
Also building
- Ekoham
The parent company. Focused software products and software-enabled services for real-world business workflows.
- Voxpilot
A software studio building AI receptionists, custom websites, and the automation that keeps calls, leads, and bookings connected.
- Tovu Studio
A booking marketplace for local appointments: find a place, read its page, and reserve a time in minutes.
Your data is not our leverage
Export any view to CSV or XLSX. Read the whole thing through an API with a token you make yourself. Getting your data back never costs money and never needs a phone call. A tool that holds your data hostage is one you were right to distrust.
The database is the boundary
Who can see what isn't a checkbox in some screen that a developer forgets to add. Postgres enforces it, one row at a time, so a bug in the interface can't hand out data it was never allowed to show. It is the least glamorous decision in the project and the one that carries the most weight.
Say what isn't built
This page and the home page only claim things that work today. No roadmap dressed up as a feature list, no “coming soon” quietly doing the selling. When a thing isn't finished, the site tells you, including on the pages meant to win you over.