What is Dvl'epr Studio?
Dvl'epr Studio is one of the Dvl'epr family of tools. Dvl'epr is a hypertext declarative platform that generates web applications from a set of declarative files — for more about the platform, see the Dvl'epr home page.
The Studio lets you build those applications visually. Everything an application needs comes together in one structured place — screen layouts, CSS, JavaScript, and the SQL behind each screen — and the Studio compiles it all into the set of XML files Dvl'epr needs to generate the finished application.
The Studio is itself a Dvl'epr application, built with the platform it builds for.
Sites
Manager
Dashboard
Contacts
ContactsList
ContactDetail
AddContact
<block> <div class="title">Contacts</div> <div type="dynamiclist" class="list"> <div type="row" class="card"> <span class="name">%contact_name%</span> <span class="role">%job_title%</span> </div> <sql> <query name="contacts"><![CDATA[ SELECT contact_name, job_title FROM contacts WHERE dept_id = '%deptid%' ]]></query> </sql> </div> </block>
Low-code
Dvl'epr Studio is a low-code tool in the literal sense: the only code you have to write is SQL. Screens are created visually, and everything that normally surrounds them — data loading, form handling, validation, page updates — is generated rather than written, on the server and in the browser alike.
What remains is the part that is genuinely yours. The queries, and whatever CSS and JavaScript your design calls for, unless your specification already supplies them. Anything truly unusual is a small plugin, and that is the exception rather than the routine.
That makes it a tool for developers and technical teams — and it means there is no ceiling. A no-code tool works until a requirement falls outside what it can express, and then there is no way through. Here the data layer stays in SQL and the output stays as editable files, so that wall never arrives.
Three things we're building
AI assistance. We already use AI to build Dvl'epr applications — the same assistance is coming to the Studio, so you build yours faster.
A SQL generator. Build your queries in the Studio instead of writing them by hand.
A fuller designer. Brought in line with visual build tools like Wix.
Each addition changes how you build, not what you get.
Not like other low-code tools
For most low-code tools, the builder is the platform. Delete it and your application has nowhere to live.
Dvl'epr Studio isn't the platform. It's the tool that writes the declarative markup Dvl'epr generates applications from — markup that can equally be written by hand, as developers have done since 2005. Delete the Studio and nothing changes: the same files, in the same place, edited the same way.
Full visual designer
Design screens exactly as they will look, with your own styling applied as you work. Create the styling here, load stylesheets you already have, or bring in HTML built in other design tools instead of rebuilding it.
Built-in data layer
SQL is attached directly to the screen that uses it. No API to build, no client library to keep in sync, and no separate data layer drifting out of step with the screens it serves.
Live preview on real data
Preview runs the real application against your own database, with your own styling — not an approximation. What you see is what deploys.
End-to-end form builder
Fields, validation, and the insert or update that saves them are built together in one place, so a form and the logic that stores it never drift apart.
Reusable components
Build a component once and reuse it anywhere in the project. Save it as a template, then reuse or adapt it wherever you need it.
View the declarative markup
See the markup behind any component from inside the Studio, at any time, without compiling or exporting the project.
From a blank project to a deployable app
Create a project
Point the Studio at your database and describe the apps and sites your users will log into.
Design the screens
Build each screen visually, with the queries that feed it written alongside.
Preview against real data
Check a screen against the test database, right in the Studio.
Export and deploy
The Studio writes the declarative markup files and the assets. Deploying is moving them to the production server, or wherever the application runs.
Built for the Dvl'epr platform
If you already build on Dvl'epr, the Studio is a faster route to the same applications — built visually rather than written by hand.
If you don't yet, it's for anyone in the business of building web applications and dynamic websites — whether for clients or for yourself.
Dvl'epr developers
Already building on Dvl'epr. The Studio is a faster, visual way to build your applications.
Freelance developers
Prototype in a day, deliver in weeks. No servers to set up and no framework to learn.
Web and digital agencies
More projects from the same team, and any developer can pick up any project.
In-house development teams
Internal tools in weeks, not quarters. Easy to change when the requirements do.
Software houses and product teams
Tailor the same product for each client quickly, without starting over every time.
Consultants and integrators
Portals, dashboards and workflow tools over a client's existing database, without a separate front-end team.
Where Studio sits
Dvl'epr is the platform. It runs your application, and it is the only part you actually need — everything the Studio produces can equally be written by hand. The Studio and Dvl'epr Cloud support it, and both are optional.
Runs your application. Reads the markup and serves the finished web application to the browser.
Builds the markup visually, instead of writing it by hand.
Hosting and publishing, so a build goes live without a server to manage.
Common questions about Dvl'epr Studio
What is Dvl'epr Studio?
What is Dvl'epr, the platform underneath it?
Is Dvl'epr Studio itself built on Dvl'epr?
Does Dvl'epr Studio lock me into the tool?
Is Dvl'epr Studio a no-code or a low-code platform?
How is it different from a no-code app builder?
What do I need to know to use Dvl'epr Studio?
Is Dvl'epr Studio suitable for vibe coders?
What is on the Dvl'epr Studio roadmap?
Is the preview accurate, or is it a mock-up?
How does an application built in Dvl'epr Studio get deployed?
Can I build forms in Dvl'epr Studio, not just screens that display data?
Can I still hand-write parts of the application?
Is Dvl'epr Studio available now?
What does Dvl'epr Studio cost?
Build something with the Studio
Early access is open to everyone building on Dvl'epr, and to a small number of developers new to the platform. Just a conversation about what you want to build.
Or email us directly at hello@dvlepr.com