Oracle 19c · ORDS · APEX
Your Oracle workbench,
served from the database.
HTMLdb Developer puts a developer console, your Jira tasks, Git and an encrypted credential vault on one page. It is PL/SQL and Vue, delivered by ORDS. There is no app server to run and nothing to install on a desk.
-- one APEX region, one PL/SQL call return htmldb_apps_pkg.html(:USER_ID); -- every request, before anything runs if not htmldb_auth_pkg.check_request( p_params => g_params, p_need_dev => true ) then ... 'Not authorized'
The overview: all four apps and how the security works, in just over a minute.
Four apps, one page
Each app lives in its own package with its own endpoints, and they share one page: switch tabs without reloading, open a task's code in the console, send a query from Git to a SQL window.
Dev console
Everything you reach for in TOAD, in a browser tab.
See every feature →
Tasks
Your Jira work, cached in the database and edited in place.
See every feature →
Git
GitHub, next to the code it holds.
See every feature →
Credential manager
Every key, token and certificate, encrypted.
See every feature →
From DEV to PRD, by pull request
- Each database knows its own repo, so Commit lands in the right one
- Compare a pull request, or compare this database against it
- An AI security review of the whole code, posted on the pull request
- Merge opens the object at the merged version; Send back returns it to DEV with the reasons
Security that starts with the database
Signed in with App Builder
Every page and every request checks the APEX session and that the browser is signed in to App Builder as a developer of the workspace. Nothing runs before that check.
Nothing trusted from the browser
Requests are POSTs to the package that owns them. The user and workspace come from the checked session; names, paths and keys are validated before they reach SQL or a URL.
Secrets stay on the server
API keys, OAuth tokens and certificates are stored AES-256 encrypted with a fresh IV for every value. The browser only ever learns whether a secret is set.
Every change reviewed
Code moves DEV to TST to PRD by pull request, with an AI security review before merge and Send back with reasons when it is not ready.
On the record
Git history for every object, an audit log for every credential change, and each database in its own colour so PRD never looks like DEV.
Built with what you already run
See it on your own database
Tell us about your Oracle environment and we will get back to you.
Get in touch