Overview
Appsmith is an open-source internal app builder for creating admin tools, CRUD apps, approval flows, and operational dashboards on top of existing APIs and databases.
In a Shakudo environment, Appsmith usually sits at the internal tools layer. Business teams use it to create interfaces over Postgres, APIs, Airbyte outputs, MinIO files, or operational services without building a full custom frontend.
This page is written for onboarding and deployment calls. It focuses on what customers need to understand, provide, validate, and troubleshoot in a real environment.
Where it fits in the stack
- Primary role: Appsmith provides a reusable platform capability rather than a one-off application.
- Typical deployment model: Kubernetes + Helm, with customer-specific values and secrets.
- Typical access model: private internal endpoint or customer-approved external route.
- Typical support model: validate deployment health first, then validate user workflow and integrations.
Getting Started
Start with one safe workflow in Appsmith before enabling production usage. The goal is to prove connectivity, permissions, and operational ownership.
What the customer needs to provide
- target data sources such as Postgres, REST APIs, GraphQL APIs, or internal services
- authentication approach for users, usually SSO/OIDC when available
- SMTP settings if email invite and password reset flows are needed
- domain name and TLS routing requirements
- initial admin owner account
First workflow
- Open Appsmith and create a workspace
- Create a datasource such as Postgres or a REST API
- Create a new app from a template or blank canvas
- Add widgets such as tables, forms, buttons, and charts
- Bind widgets to queries/actions and test with sample data
- Publish the app and share it with the right users
Administration and Best Practices
Use these practices to keep Appsmith reliable after the initial deployment.
- Disable public signup unless the customer explicitly wants self-serve users
- Use groups and roles to separate editors, viewers, and app owners
- Keep production apps connected to read-only database users unless write access is required
- Export important apps before major upgrades
- Avoid embedding shared admin credentials in queries
- Use environment-specific datasources for dev, staging, and production
Troubleshooting & FAQ
Use this section during customer debugging calls. Format: Problem → What to check → Fix.
Datasource connection fails
- What to check: Check host, port, username, password, SSL mode, and network route from the Appsmith pod
- Fix: Update the datasource config and test connection before publishing the app
Published app loads but query returns empty data
- What to check: Check query parameters, widget bindings, and selected environment
- Fix: Run the query directly in Appsmith and confirm the widget is bound to the right response field
Users cannot log in
- What to check: Check signup settings, SSO/OIDC config, invite status, and email delivery
- Fix: Use an admin account to invite the user again or correct the SSO redirect URL
App is slow
- What to check: Check query runtime, API latency, page widget count, and database indexes
- Fix: Paginate large tables and move expensive joins into database views
