Release notes, announcements, and stories from the team.
Every prompt you send an AI coding agent costs tokens, and a surprising share of them go to the backend: schemas, policies, generated types, redeploys.
In the last article we said a Skapi project in São Paulo runs at a fraction of what a traditional server backend costs there, and that getting there was hard.
skapi.com has a new look, and the dashboard behind it was rebuilt page by page. This is a short tour of the parts you will notice first: a database you can search from one bar, an…
Skapi now runs in Brazil. São Paulo is our newest region, and it is the first place in South America where a project's database, its files and its user accounts all live on the…
skapi-js 2.0.0 reached npm on September 4. In the twenty days after it we published more releases. This is a short account of the ones that matter, and of why the work did not…
Every plan now has a monthly bandwidth allowance, storage moves from the database to the file pool, and a project that outgrows its plan is suspended instead of quietly stuck.
Skapi now runs in France. Paris is our newest region, and it is the first place in Europe where a project's database, its files and its user accounts all live on European ground.
Update: the database, file storage and bandwidth numbers in this post are being replaced. Every plan gets a monthly bandwidth allowance, and a Free or Standard project over a sto…
Most backends will tell you your data is "encrypted at rest." What that phrase usually means is that the hosting provider holds a key, the database holds your data, and the two…
The stable tag has moved: npm i skapi-js installs 2.0 today. Private records can now be encrypted in the browser, under your user's own password.
Your AI assistant does not burn tokens on your app. It burns them on your infrastructure.
Skapi 2.0 is installable today as a release candidate. It is a stability and performance release: a naming change, one genuinely new method, and a long run of fixes behind both.