About
Software should be describable, not assembled
Most people who need a small piece of software do not need a framework, a hosting account and six weeks. They need the thing itself. Vixtur exists to make the distance between describing it and using it as short as it can honestly be.
What it actually is
Vixtur is an app builder. You describe what the system has to do and for whom, and it writes a whole project: tables with real fields, sign-up and sign-in for your own users, permission rules the server checks on every request, and a public address you can send to somebody the same day.
It is not a page builder with a form on it, and it is not a chat that hands you a zip file. What comes out is a running application with a database behind it and a version history you can walk back into.
Four rules it is built to
These are not values on a wall. Each one is a decision that is visible in the product, and each links to the page that has to keep it — so if one ever stops being true, that page is where it breaks first.
- A failure is not billedCode that does not run is not saved, and what is not saved is not charged for — including the automatic repair rounds that tried to rescue it. The charge is worked out from tokens that were actually measured, after a version passed its health check.How the price is decided
- No database key in the browserNothing in an app built here reaches a record with a key that shipped to the page. The server is the only door, and it checks the table's rule on every request rather than trusting what the client asked for.How the security works
- The ceiling is yoursA limit per build, per day and per month, set by you. When it is reached the work stops. It does not carry on and send you a bill afterwards.See the plans and the ceilings
- Nothing is shown that was not checkedA template appears in the catalogue only after a browser loaded it and walked its pages without a single console error. The date on every card is when that happened, not when somebody wrote the entry.Open the catalogue
Two languages, on purpose
The product was written for Hebrew first, and Hebrew is a right-to-left language with square, close-fitting letterforms — which is not a translation problem, it is a layout one. Every screen here is built to be read in either direction rather than translated into one and patched for the other.
The public site answers at two addresses, one per language, and both are real pages with their own text in the HTML. Neither is a redirect to the other.
If something here is wrong, say so
Every claim on this site is meant to be checkable against the product. If you find one that is not, that is a defect and we would rather hear it than not.