Start with one useful team workflow
Choose a specific problem and the people who need the result. Involve a technical owner for configuration and access, then validate the workflow with its users.
MolternInternal tools
Solutions
Small tools deserve a proper home.
Run the dashboards, portals and workflows that make a particular team’s work easier.
Flight paths artwork / 12
An internal tool does not need to become a commercial product to matter. Give it a named owner, an appropriate environment and clear access. Start with a catalog service or deploy your own application, then connect only the data it needs.
Put it into practice
Choose the supporting software
The catalog includes data, automation, AI, monitoring and other packaged software. Read each service guide before deployment and review its configuration and dependencies.
Grant the access a task needs
Use managed roles and the narrowest useful scope. Set expiry for temporary access, inspect effective permissions and revoke the grant when the work is finished.
Detailed instructions are maintained in the product documentation.
Questions before you start
Can a non-developer start a project?
A business team can define the need and explore services. Involve an authorized technical owner for deployment and sensitive configuration.
Does every service have the same setup?
No. Required variables, dependencies, storage and access differ. The individual service guide explains the setup.
Does using a secret allow someone to reveal it?
Secret use and secret reveal are separate permissions. Grant sensitive access only when the task requires it.
Keep exploring
All pages ↗
Start with one useful workload.
Bring your code or choose a service, then give the result a clear operating home.
Start building ↗