Questions
Questions and answers
Where the answer is "not yet", it says so.
About Albitor
What is Albitor?
A service that builds software from a written brief. You describe the tool you need, Albitor builds it and puts it live, and you get the running tool and all of its code.
Who is it for?
Anyone who needs a working app and doesn't want to run a development project to get one: people building something for themselves, small businesses, teams inside larger organisations, and developers who want a head start. There is more for government and financial services teams.
Do I need to be technical?
No. You write the brief in plain English, answer the questions Albitor raises, and pick a design. You never have to read or write code.
Can I see it working first?
Yes. How it works follows one real build step by step. Email hello@albitor.com to see a finished build.
Building a tool
What goes in a brief?
What the tool is for, who will use it, and what they need to do with it. Say what matters most if something has to give, and name any outside service the tool must use, such as Companies House. The Kickoff brief is a good example.
How long does a build take?
It depends on the size of the app. One with around ten user journeys, such as a customer onboarding tracker, is built and through its assurance checks in a few hours.
What if Albitor gets something wrong?
It asks before it assumes, and it waits for you to choose the design. Every part is checked before it goes live. Once the tool is running, you can ask for a change.
Can we choose the programming language?
Not during the beta. Apps are built with Svelte for the screens, Go for the server and Terraform for the infrastructure. After the beta you'll be able to choose.
Hosting, code and data
Do I need my own infrastructure?
No. Albitor can run the app for you. If your organisation needs the app and its data on its own infrastructure, Albitor deploys it there instead.
Will it work on my phone?
Yes, in the phone's browser. Every app is built for desktop and phone widths, and you preview both before anything is built. Apps for the App Store and Google Play are not available yet.
Where does my tool run?
On Albitor, or on your own infrastructure. If Albitor hosts it, there is nothing for you to set up. If you need the tool and its data on your own infrastructure, Albitor deploys it there.
Who owns the code?
You do, wherever the tool runs. You can download the whole codebase at any time, with its documentation and a handover pack written for whoever looks after it next.
Can our own developers change it later?
Yes. It is ordinary source code, and the handover pack explains how it fits together.
Which AI models build our app, and where do they run?
Albitor picks the models and providers for each build, currently open-weight models served mainly by Fireworks. Your organisation's admin can instead choose which models and providers are allowed, including providers locked to a region. The sub-processors page lists every provider.
The model sees your brief and your app's code. It never sees the values of your keys or passwords. Your finished app only calls a language model if you ask it to.
Security and assurance
What is each tool checked against?
The standards come from the plugins and profile you choose for the project. An internal tool, for example, is checked for accessibility against WCAG 2.2 AA and for security against OWASP ASVS, with scans for leaked secrets and vulnerable dependencies. Custom plugins can add your own policies and checks. A mandatory check that fails, or can't prove that it passed, stops the build.
Does a tool meet the Government Service Standard?
Not yet. Checks run against the standards your project's plugins set, and a full Service Standard assessment is future work.
Pricing
What does it cost?
You pay for building, in credits, and a credit costs £1 including VAT. Top-ups don't expire while your account is open. The pricing page has the detail.
This website
Does this website track me?
No. It sets no cookies and runs no analytics, and every font and image is served from this site. The server keeps a standard log of requests to keep the site running. The privacy notice covers what that log holds.
Is this website accessible?
It is built to meet WCAG 2.2 AA. The accessibility statement explains how it is tested and how to report a problem.