We take our trust in our users seriously. This is why existing apps are supported until August 31st, 2027 (1 year, 10 days away). Backups will stay available until August 31st, 2028 (2 years). The product is full open source, and we put a lot of work in making it easy to self-host.

August 31st, 2027 is 1 year and 10 days away.

This is an exciting project! My main feedback: you can definitely tell the website content is AI-generated. It's okay to vibe code the design, but I really hesitate when I see vibed writing.

You're right, putting more attention to that now.

Re-read and it reads a lot better, good work!

Nice! Would love a brief explanation of the infrastructure. I see the Powered by "Upstash Redish Search", but why choose Upstash Redis Search vs something else?

Interesting idea! Question:

> It is highly unlikely that an AI agent startup becomes wealthy by creating the best harness for a particular use case.

If it's not the harness, what do you think is the thing that will differentiate AI agent startups? Is it mainly data, or something else?

The most valuable pieces of information an AI agent startup can gather is access to their customer's proprietary data and knowledge of their customers preferences (memory + self-learning).

Even as the cost of writing code goes to zero, those two pieces of information are non-commodities.

It’s interesting that Claude chose to hint, rather than reveal the full truth or to lie.

I wonder what in the training / system prompt causes Claude to do this.

I don't quite understand, what would 100K buy you?

AFAIK you would get about ~5 concurrent users, with a max context window of ~128K tokens on the larger models.

This wouldn't be good enough for coding -- are you guys thinking of using it for something else?

By my calculations 100k could get you 18 5090's + compute to host them, or 18 96gb Mac mini's. You can get a lot of context window and users out of that setup.

Gigabyte 4x AMD Instinct MI300A rack server (512GB GPU RAM total)

Roughly equivalent to 4x H200's for less than half the price.

Vaguely around 60k tokens per second...

Instant gives you a database, but it also gives you a sync engine that you can use in the frontend. We included this instruction because you would ideally use this to build an app.

Right but it's not your responsibility to direct the UI. Your responsibility is backend services, possibly at a stretch, the architecture of apps as they relate to using those backend services, but it's most definitely not the aesthetics.

What if the app is headless and the LLM tries to stick a UI on it? What if the app is a TUI and the LLM gets stuck on terminal fonts? What if my UI aesthetic is grungy hackercore and the LLM tries to make it look like every other Tailwind website?

This criticism/feedback is less about what's written, and more about why it was deemed appropriate. You're getting direct input to the development process of your customer's products, and you're using that responsibility to... make pointless comments about design?

Currently we recommend folks to write a script with the admin sdk. Efficient import / export is on the roadmap!

The UUID doesn’t actually affect the response. Every GET request still generates unique credentials each time, no matter what the value is that passes to /provision/<uuid>

We added it to help the app builders that do a lot of caching get unique responses. Turns out even if you set no-store cache headers, some app builders cache the pages. We tested this idea with those app builders and saw that they did generate uuids each time.