Accounts are created on a request basis. Contact
[email protected] to request an account.
After creating an account, the same email address can
be used to request that additional employees get
registered.
By default, one employee is registered per micro UI,
which puts the account on a free tier.
If the same email address is used for the different
micro-UIs, this still counts as one employee and thus the
account will remain in the free tier.
Different button on the 'Navigation' section represents
different micro-UI. Each micro-UI has it's own sign-in and thus
a unique password, even if the same
email address is for different micro-UIs.
Finally, after creating an account, remember to stay
in touch with customer support (complaints, questions,
comments, etc.).
Get software development and support for your applicaiton, if you're willing to use the system while it is in its earlier phases. The early adopters program is currently the only way to access the system and access is limited to building web apps (i.e. the python server is not yet available).
Contact [email protected] to apply.
"The future is built by passion and perseverance in the present"
Get inspired by some Video Tutorials.
By using the Development Web App, you agree to our terms and services.
The development web app system is a cloud-based development environment. It allows developers to code freely, while benefiting from built in automations that assist in various parts of the development process.
The system serves as a solid foundation on which to build
almost anything that can run on the cloud. This might be
as simple as a static website or as complex as a web app
with multiple micro-UIs, databases, and API servers.
Simplicity is a key principles of the
development web app system.
The system aims to be user-friendly enough to be useful for
non-technical researchers or business analysts (provided that
they are willing to learn basic
JavaScript, HTML, and SQL). This simplicity also assists
advanced users, by eliminating repetative tasks and reducing
surface area for bugs, which together radically
cut development times.
Flexibility is another key principle. The development web app
was built with complexity in mind, therefore
significant effort has
gone into making sure that the system does not limit or
frustrate advanced developers who may be working on extremely complex
problems. This is done by allowing standard thrid party
integrations (e.g. users can download
and use any npm or pip dependency to interact with a thrid party).
For exteremely custom processes, a seperate manually managed
deployment can be made and then developers can
connect to that system with the system that they
build on the development web app. This may sound like more work,
but at the level of complexity where this becomes necissary
this splitting up is actually beneficial because it adds modularity.
The development web app system might be useful for, e.g.
In a commercial context, improving an enterprise's
value-proposition
can make all the difference, resulting in 100 times as many
customers and therefore e.g. 100 times as much profit, or more.
On the other hand, if the given enterprise were to
rather focuses its effort on
setting up a completly custom development environment, this
might slightly reduce running costs, which might
result in e.g. 1.5 times
as much profit,
while also increasing complexity, risks of downtime, data
loss, and delays.
Extra: Even a non-commercial context, it is equally not benefical to
re-invent the wheel. Instead, it may be advised to focus on
strategic objectives.
Furthermore, choosing a pre-setup environment may very well be
the difference between achieving
a goal and not achieving anything at all, in situations
where there isn't money
to hire professionals to solve complex technical challenges.
There is no hard vendor lock-in, the codebase is compiled in a
way that is legible and that follows industry standard practices.
The output is a Kubernetes deployment that uses
Docker Images, which are primarily based on: Node.js, Python,
and Postgres. This setup allows for
distributed computing to practically any scale.
Users add their own API keys for computing resources. This
means that any resource usage is paid directly by the user without
any additional markup from the system. The primary
thrid party that the system expects API keys for is Google Cloud.
Developers can connect
to any external thrid party using standard API calls. Third
parties could be anything from a STMP mail server, an external
NoSQL database, or even a set of high-performance computing
resources.
The system can be used for, but is not ideal for, design
focused static websites. No-code tools may be better,
unless there are plans to increase backend complexity at
some later date.
All management tasks (e.g. task assignment and communications about
strategic objectives) should be done externally, using generic
external tools (or tools you build for yourself using the
development web app).
A build process is required for
for changes to reflect on the testing instance. It is
therefore recommended that an editor such as
VS code is used in combination with the system (see the video
tutorials for more guidence on best practices).
To benefit from the LLM explosion, LLM coding assistants can be used
in VS code (before copying code over to the system).
Generic LLMs can also be manually queried on their official web pages,
to assist with various tasks
such as debugging, doing research, or coming up with ideas.
Using generic LLMs that don't have context over the codebase
can ensure that employees understand the context themselves.
It can also incentivise writing clean code (and cleaning
code when necissary),
instead of relying on LLMs to understand an every increasinly
messy codebase.
Extra: Among many other things, the development web app
can be used to design
multi-agent LLM system or to build and train custom
AI models. To do this, API calls to thrid
parties may be needed to access propriotery LLMs
or to access high-performance
computing resources (when running open-source LLMs or your own
propriotery models).
1 employee
Free
Generic sales support only
Full access to the system
Less than 5 employees
€2 000 monthly fee
Developer support
Full access to the system
Less than 10 employees
€5 000 monthly fee
Developer support
Full access to the system
10 or more employees
€10 000 monthly fee
Priority developer support
Full access to the system
Regardless of your organisation's size, feel free to start on the free tier and work your way up as needed.