diff --git a/apps/website/app/industries/agencies/page.tsx b/apps/website/app/industries/agencies/page.tsx new file mode 100644 index 0000000..4c6c627 --- /dev/null +++ b/apps/website/app/industries/agencies/page.tsx @@ -0,0 +1,203 @@ +import { + IndustryPage, + type IndustryPageData, +} from "@/components/industries/IndustryPage"; +import { + Bot, + Eye, + FolderKanban, + GitBranch, + Globe, + Paintbrush, +} from "lucide-react"; +import type { Metadata } from "next"; + +export const metadata: Metadata = { + title: "Deployment Agency Platform for Client Apps", + description: + "Run client apps, previews, and production releases from one deployment agency platform that supports Git, Docker, domains, logs, and databases.", + alternates: { + canonical: "https://dokploy.com/industries/agencies", + }, +}; + +const data: IndustryPageData = { + hero: { + title: "A deployment agency platform for faster client launches", + description: + "Launch client websites, SaaS products, internal tools, vibe-coded software, and campaign apps without rebuilding the deployment process every time. Dokploy gives agencies a repeatable release platform with previews, domains, logs, databases, and client-ready governance.", + }, + features: { + heading: "Ship client projects faster without messy hosting handoffs", + description: + "Agencies need a deployment model that works across clients, stacks, domains, and production requirements. Dokploy helps teams move from repo to live app with less manual setup and more visibility after launch.", + items: [ + { + icon: GitBranch, + title: "Launch client projects from Git", + description: + "Connect GitHub, GitLab, Bitbucket, Gitea, generic Git, Docker, or Docker Compose. Teams can deploy new client apps without writing custom server instructions each time.", + }, + { + icon: FolderKanban, + title: "Separate each client into projects", + description: + "Organize services by client, brand, product, or retainer. Clear project structures make it easier to manage access, environments, and ownership as your portfolio grows.", + }, + { + icon: Eye, + title: "Preview work before client signoff", + description: + "Use preview deployments to show working application changes before they’re merged. Account teams and clients can review the app in context.", + }, + { + icon: Globe, + title: "Manage domains and production releases", + description: + "Configure domains, environment variables, logs, and deployment history from one platform. Keep launch tasks close to the service, not spread across tools.", + }, + { + icon: Bot, + title: "Enable AI workflows with the MCP", + description: + "Connect your AI agent to Dokploy with the MCP, so team members and clients can manage deployments with prompts, or even autonomously.", + }, + { + icon: Paintbrush, + title: "Whitelabel for a single brand experience", + description: + "Enterprise whitelabeling can help agencies present a branded deployment experience, while giving clients more security.", + }, + ], + }, + comparison: { + heading: "Client deployments without a patchwork of hosting accounts", + description: + "Dokploy gives your software building and deployment agency a single operating model to build, review, launch, and support client apps.", + without: { + title: "Traditional agency deployment tools", + items: [ + "Every client can use a different provider or server setup.", + "Launch checklists depend on whoever configured the project.", + "Preview links, logs, domains, and backups sit in different places.", + "Support teams need to learn each client’s hosting account.", + "Handoffs can create confusion over access and ownership.", + ], + }, + withDokploy: { + title: "Dokploy for agencies", + items: [ + "One platform for client projects, environments, services, and servers.", + "Git and Docker workflows support a wide range of project stacks.", + "Preview deployments make sign-off easier before production release.", + "Domains, logs, monitoring, backups, and rollbacks are managed close to the app.", + "Enterprise options support SSO, custom roles, audit logs, and whitelabeling.", + ], + }, + }, + workflow: { + heading: "From client repository to production launch", + description: + "Dokploy helps agencies turn deployment into a repeatable client delivery process. New projects can follow the same workflow, even when the technology stack changes.", + steps: [ + { + title: "Create the client project", + description: + "Set up a project for the client, campaign, product, or retainer. Add environments for development, preview, staging, and production as needed.", + flow: "Create project → Add environments → Invite team", + }, + { + title: "Connect the repository", + description: + "Connect the client app from Git or configure a Docker-based deployment. Dokploy can trigger releases from webhooks when changes are pushed.", + flow: "Select provider → Choose repository → Set branch", + }, + { + title: "Share a preview", + description: + "Deploy a preview environment so account teams and clients can review the live app before release. Keep feedback tied to the version under review.", + flow: "Open preview → Share URL → Collect signoff", + }, + { + title: "Launch and support", + description: + "Assign domains, deploy to production, and monitor logs and metrics after launch. Rollbacks and deployment history help support teams respond quickly.", + flow: "Add domain → Deploy → Monitor", + }, + ], + }, + builtFor: { + heading: "Built for agencies managing many client apps", + paragraphs: [ + "Dokploy gives agencies a cleaner way to manage multiple apps, clients, and release workflows.", + "Teams can deploy from common Git providers, use Docker Compose for more advanced projects, and keep client services visible after the initial launch.", + "For larger agencies, Enterprise features add SSO, custom roles, audit logs, and whitelabeling, making it easier to give internal teams and client stakeholders the right level of access without handing over raw server credentials.", + ], + screenshotAlt: + "Dokploy dashboard showing agency projects grouped by client, with one app open to preview deployments, production domains, logs, monitoring, and database services", + }, + detailRows: [ + { + area: "Deployment methods", + support: + "Git, Docker, Docker Compose, Nixpacks, Heroku Buildpacks, and custom Dockerfiles", + }, + { + area: "Client workflows", + support: + "Preview deployments, environments, templates, domains, and webhook-based auto deploys", + }, + { + area: "Access control", + support: "Owner, Admin, and Member roles, with custom Enterprise roles", + }, + { + area: "Agency options", + support: + "Enterprise SSO, audit logs, whitelabeling, and client-friendly role management", + }, + { + area: "Databases", + support: "PostgreSQL, MySQL, MongoDB, Redis, and MariaDB", + }, + { + area: "Operations", + support: + "Monitoring, logs, backups, rollbacks, remote servers, MCP, and multi-server management", + }, + ], + faqs: { + heading: "Deployment agency platform FAQs", + items: [ + { + question: "What is a deployment agency platform?", + answer: + "A deployment agency platform is software that helps agencies deploy, manage, and support client applications across multiple projects. Dokploy gives teams one place for apps, environments, domains, logs, databases, and deployments.", + }, + { + question: "Can Dokploy handle multiple client projects?", + answer: + "Yes. Agencies can organize projects around clients, products, campaigns, or retainers. Each service can have its own environment variables, domains, deployments, logs, monitoring, and backups where relevant.", + }, + { + question: "Can clients review apps before production?", + answer: + "Yes. Preview deployments help agencies share live versions of changes before they are merged or released. This makes signoff easier for websites, SaaS products, and custom apps.", + }, + { + question: "Does Dokploy support whitelabeling?", + answer: + "Dokploy Enterprise includes whitelabeling for self-hosted setups, along with SSO, custom roles, and audit logs.", + }, + { + question: "Can agencies deploy Docker Compose apps?", + answer: + "Yes. Dokploy supports Docker Compose for multi-service applications, which is useful when client projects include APIs, databases, workers, queues, or supporting services.", + }, + ], + }, +}; + +export default function AgenciesPage() { + return ; +} diff --git a/apps/website/app/industries/finance-banking/page.tsx b/apps/website/app/industries/finance-banking/page.tsx new file mode 100644 index 0000000..0105ccb --- /dev/null +++ b/apps/website/app/industries/finance-banking/page.tsx @@ -0,0 +1,197 @@ +import { + IndustryPage, + type IndustryPageData, +} from "@/components/industries/IndustryPage"; +import { Activity, Bot, Eye, GitBranch, Lock, Users } from "lucide-react"; +import type { Metadata } from "next"; + +export const metadata: Metadata = { + title: "Private Deployment in Finance Software", + description: + "Keep banking apps, internal tools, and fintech services in controlled environments with private deployment in finance that your teams manage.", + alternates: { + canonical: "https://dokploy.com/industries/finance-banking", + }, +}; + +const data: IndustryPageData = { + hero: { + title: "Private deployment in finance for safer app releases", + description: + "Deploy internal banking tools, fintech services, and customer-facing apps without giving up control of infrastructure. Dokploy gives financial technology teams a governed platform for private deployment and ongoing operations.", + }, + features: { + heading: "Ship regulated software without slowing release teams", + description: + "Financial institutions need software teams to move quickly, but deployments need clear boundaries. Dokploy lets developers release from Git and Docker-based workflows while platform teams manage access, environments, logs, and rollback paths.", + items: [ + { + icon: Lock, + title: "Control releases inside private infrastructure", + description: + "Run banking apps, internal tools, and fintech services on infrastructure you control. Self-host the full platform when internal teams need complete ownership.", + }, + { + icon: GitBranch, + title: "Connect Git workflows to governed deployments", + description: + "Deploy from GitHub, GitLab, Bitbucket, Gitea, generic Git, Docker, or Docker Compose. Teams keep familiar workflows.", + }, + { + icon: Users, + title: "Separate teams with roles and environments", + description: + "Create projects around business units, teams, or platforms. Permissions, SSO, custom roles, and audit logs keep access aligned with finance governance.", + }, + { + icon: Eye, + title: "Review changes before customer impact", + description: + "Use preview and staging environments to test pull requests, policy updates, and product changes before release. Reviewers don’t have to rely on code diffs.", + }, + { + icon: Activity, + title: "Monitor services across servers", + description: + "Track application health, server metrics, logs, domains, and deployments from one platform, so platform teams have clear visibility.", + }, + { + icon: Bot, + title: "Power your AI deployment process", + description: + "Build AI sandboxes where even your non-technical team members can test vibe-coded software in a secure, controlled environment.", + }, + ], + }, + comparison: { + heading: "Private deployment without cloud account sprawl", + description: + "Separate cloud accounts can work for individual projects, but they become difficult to govern across banking products, internal tools, and compliance-sensitive workflows. Dokploy centralizes the deployment layer while keeping teams productive.", + without: { + title: "Generic cloud accounts", + items: [ + "Teams may need broad infrastructure permissions.", + "Release processes vary between products and departments.", + "Cost, cleanup, and access reviews become harder to manage.", + "Logs, rollbacks, domains, and backups can sit in different tools.", + "Security teams have limited visibility into smaller internal apps.", + ], + }, + withDokploy: { + title: "Dokploy for finance and banking", + items: [ + "Applications deploy inside controlled public, private, or self-hosted environments.", + "Admins manage projects, users, services, and servers centrally.", + "Teams can use Git, Docker, Docker Compose, and supported databases.", + "Enterprise options include SSO, custom roles, audit logs, and whitelabeling.", + "Finance teams get repeatable workflows across internal and customer-facing apps.", + ], + }, + }, + workflow: { + heading: "From financial app repository to controlled release", + description: + "Dokploy turns release management into a clear workflow. Developers can ship from their repositories, while platform teams keep the environment, access model, process, and release path consistent.", + steps: [ + { + title: "Create the regulated environment", + description: + "Set up a project for a banking service, internal tool, fintech app, or shared platform. Use separate environments for development, review, staging, and production.", + flow: "Create project → Add environment → Assign owners", + }, + { + title: "Connect the repository", + description: + "Connect a Git provider or bring a Docker-based deployment. Dokploy can trigger deployments through webhooks when approved changes are pushed.", + flow: "Select provider → Choose repository → Set branch", + }, + { + title: "Review before release", + description: + "Deploy changes into a preview or staging environment for product, security, and platform review. Stakeholders can test the running service before it reaches customers or staff.", + flow: "Open preview → Check logs → Approve release", + }, + { + title: "Deploy and monitor", + description: + "Promote the release, watch logs and metrics, and use rollback options if the service needs to be restored. The full deployment history stays tied to the service.", + flow: "Deploy → Monitor → Roll back if needed", + }, + ], + }, + builtFor: { + heading: "Built for banking platforms, internal tools, and fintech teams", + paragraphs: [ + "Dokploy gives finance teams a practical middle ground between unmanaged cloud hosting and heavy internal platform projects.", + "Developers can keep simple release workflows, while infrastructure owners retain control over servers, access, domains, databases, and operational visibility.", + "Teams can run Dokploy in the model that fits their requirements. Use Dokploy Cloud when you want the control plane managed by Dokploy and apps running on your own servers, or choose self-hosting when the full platform should stay under internal operations.", + ], + screenshotAlt: + "Dokploy project dashboard for a banking platform with environments for review, staging, and production, plus visible deployments, logs, monitoring, domains, and rollback history", + }, + detailRows: [ + { + area: "Deployment methods", + support: + "Git, Docker, Docker Compose, Nixpacks, Heroku Buildpacks, and custom Dockerfiles", + }, + { + area: "Git workflows", + support: + "GitHub, GitLab, Bitbucket, Gitea, generic Git, and webhook-based auto deploys", + }, + { + area: "Access control", + support: "Owner, Admin, and Member roles, with custom Enterprise roles", + }, + { + area: "Governance options", + support: + "Enterprise SSO, audit logs, whitelabeling, and role-based access control", + }, + { + area: "Databases", + support: "PostgreSQL, MySQL, MongoDB, Redis, and MariaDB", + }, + { + area: "Operations", + support: + "Monitoring, logs, backups, rollbacks, preview deployments, MCP, and remote server management", + }, + ], + faqs: { + heading: "Finance and banking deployment FAQs", + items: [ + { + question: "What is private deployment in finance?", + answer: + "Private deployment in finance means releasing applications into environments that a financial organization can control, govern, and monitor. It can apply to banking tools, fintech products, internal APIs, customer portals, and data-backed services.", + }, + { + question: "Can Dokploy support internal banking tools?", + answer: + "Yes. Dokploy can deploy internal tools, dashboards, APIs, background services, and database-backed applications from the same platform. Teams can use self-hosted or managed control-plane models depending on infrastructure policy. Dokploy empowers finance teams to build and test internal tools, including vibe-coded and AI-powered apps, in safe sandbox environments.", + }, + { + question: "Does Dokploy support SSO and access control?", + answer: + "Dokploy Enterprise includes single sign-on, custom roles, audit logs, and whitelabeling. These options help platform teams define who can view, deploy, manage, or audit services.", + }, + { + question: "Can finance teams use Docker Compose with Dokploy?", + answer: + "Yes. Dokploy supports Docker Compose for more complex services, including applications that need multiple containers, databases, queues, or supporting infrastructure.", + }, + { + question: + "Should financial institutions choose Dokploy Cloud or self-hosted Dokploy?", + answer: + "Use Dokploy Cloud when you want Dokploy to manage the control plane while your apps run on your own servers. Choose self-hosted Dokploy when your institution wants to operate the full platform internally.", + }, + ], + }, +}; + +export default function FinanceBankingPage() { + return ; +} diff --git a/apps/website/app/industries/healthcare/page.tsx b/apps/website/app/industries/healthcare/page.tsx new file mode 100644 index 0000000..9feb6a2 --- /dev/null +++ b/apps/website/app/industries/healthcare/page.tsx @@ -0,0 +1,197 @@ +import { + IndustryPage, + type IndustryPageData, +} from "@/components/industries/IndustryPage"; +import { Activity, Bot, Eye, KeyRound, Layers, Lock } from "lucide-react"; +import type { Metadata } from "next"; + +export const metadata: Metadata = { + title: "Healthcare Deployment Software for Teams", + description: + "Use healthcare deployment software to release patient portals, clinical tools, and internal apps in private environments your team controls.", + alternates: { + canonical: "https://dokploy.com/industries/healthcare", + }, +}; + +const data: IndustryPageData = { + hero: { + title: "Healthcare deployment software for safer clinical apps", + description: + "Deploy patient-facing apps, clinical operations tools, and healthcare technology in environments your IT teams can govern. Dokploy supports private deployment in healthcare with self-hostable infrastructure, access control, and review workflows.", + }, + features: { + heading: "Release healthcare technology without exposing infrastructure", + description: + "Healthcare technology deployment needs a balance between speed and control. Dokploy enables developers to publish apps efficiently while IT teams keep infrastructure, access, and operational visibility in one place.", + items: [ + { + icon: Lock, + title: "Deploy clinical apps inside controlled environments", + description: + "Run patient portals, care team tools, internal dashboards, and service APIs in environments managed by you with self-hosted Dokploy.", + }, + { + icon: KeyRound, + title: "Protect access with SSO and roles", + description: + "Separate administrator, developer, and reviewer permissions. Enterprise teams can add SSO, custom roles, and audit logs for stronger operational control.", + }, + { + icon: Eye, + title: "Review changes before they affect care teams", + description: + "Use preview deployments or staging environments to test changes before they reach staff or patients. Teams can check the running application, not just a branch or ticket.", + }, + { + icon: Layers, + title: "Support full-stack healthcare tools", + description: + "Deploy frontends, APIs, background services, and Docker Compose stacks. We also support common databases used in healthcare technology projects.", + }, + { + icon: Activity, + title: "Monitor applications and servers centrally", + description: + "View logs, deployments, and monitoring from one platform. IT teams get a clearer view of application health without manually checking each server.", + }, + { + icon: Bot, + title: "Ship AI-powered tools securely", + description: + "Build AI sandboxes where even your non-technical team members can test vibe-coded and AI-enabled software in a secure, controlled environment.", + }, + ], + }, + comparison: { + heading: "Private deployment in healthcare on one platform", + description: + "Dokploy gives teams a more consistent way to release and operate healthcare software, rather than a mix of internal servers, cloud projects, vendor portals, and one-off deployment scripts.", + without: { + title: "Ad hoc healthcare deployments", + items: [ + "Different teams may use different hosting accounts and release scripts.", + "Clinical tools can be hard to monitor after launch.", + "Access reviews depend on the process behind each app.", + "Rollbacks and backups may not be planned consistently.", + "Internal apps can become difficult for IT teams to support.", + ], + }, + withDokploy: { + title: "Dokploy for healthcare deployment", + items: [ + "Applications deploy through one governed platform.", + "Teams can use Git, Docker, Docker Compose, and supported databases.", + "Enterprise controls include SSO, custom roles, audit logs, and whitelabeling.", + "Preview deployments help teams review changes before release.", + "Monitoring, logs, backups, and rollbacks sit closer to the deployment workflow.", + ], + }, + }, + workflow: { + heading: "From healthcare app repository to governed release", + description: + "Dokploy gives healthcare technology teams a repeatable path from code to a running application. Developers can keep working from Git while IT teams manage the release environment.", + steps: [ + { + title: "Create the application environment", + description: + "Set up a project for a patient portal, internal tool, integration service, or care operations app. Use separate environments for review, staging, and production.", + flow: "Create project → Add environment → Assign team", + }, + { + title: "Connect the codebase", + description: + "Connect a Git provider or bring a Docker-based configuration. Dokploy supports common deployment methods, so teams can match the workflow to the application stack.", + flow: "Select provider → Choose repository → Set branch", + }, + { + title: "Test before release", + description: + "Deploy changes into a preview or staging environment. Product owners, IT, and clinical operations teams can review the running application before it is promoted.", + flow: "Open preview → Review service → Approve release", + }, + { + title: "Deploy with visibility", + description: + "Publish the approved version, then monitor logs, deployments, and server metrics. Rollback options help teams respond if a release needs to be restored.", + flow: "Deploy → Watch logs → Roll back if needed", + }, + ], + }, + builtFor: { + heading: "Built for patient-facing apps and internal healthcare platforms", + paragraphs: [ + "Dokploy gives healthcare technology teams a practical deployment layer for apps that need tighter operational control.", + "Teams can deploy services from Git or Docker, manage domains and environments, and keep logs, monitoring, and releases close to the application.", + "For organizations with stricter infrastructure needs, Dokploy can be self-hosted. Teams that want Dokploy to manage the control plane can use Dokploy Cloud while connecting their own servers for application workloads.", + ], + screenshotAlt: + "Dokploy dashboard for a healthcare technology project with environments for clinical-review, staging, and production, plus deployment logs, monitoring, domains, and database services", + }, + detailRows: [ + { + area: "Deployment methods", + support: + "Git, Docker, Docker Compose, Nixpacks, Heroku Buildpacks, and custom Dockerfiles", + }, + { + area: "Healthcare workflows", + support: + "Preview deployments, staging environments, webhook deploys, and production releases", + }, + { + area: "Access control", + support: "Owner, Admin, and Member roles, with custom Enterprise roles", + }, + { + area: "Governance options", + support: + "Enterprise SSO, audit logs, whitelabeling, and role-based access control", + }, + { + area: "Databases", + support: "PostgreSQL, MySQL, MongoDB, Redis, and MariaDB", + }, + { + area: "Operations", + support: + "Monitoring, logs, backups, rollbacks, remote servers, MCP, and multi-server management", + }, + ], + faqs: { + heading: "Healthcare deployment software FAQs", + items: [ + { + question: "What is healthcare deployment?", + answer: + "Healthcare deployment is the process of releasing healthcare applications, internal tools, patient portals, clinical software, and supporting services into environments that healthcare IT teams can manage.", + }, + { + question: + "How is healthcare technology deployment different from general software deployment?", + answer: + "Healthcare technology deployment often needs tighter control over access, infrastructure, review workflows, and operational visibility. Dokploy helps by keeping releases, environments, logs, monitoring, and access management closer together, while also offering self-hosted deployment.", + }, + { + question: "Can Dokploy support private deployment in healthcare?", + answer: + "Yes. Dokploy can be self-hosted, and Dokploy Cloud lets teams connect their own servers while Dokploy manages the control plane. This gives healthcare teams options for private deployment in healthcare environments.", + }, + { + question: "Can healthcare teams review apps before release?", + answer: + "Yes. Preview deployments and staging environments help teams test a running application before it reaches staff, patients, or operational users.", + }, + { + question: "Does Dokploy support healthcare app databases?", + answer: + "Yes. Dokploy supports common databases, including PostgreSQL, MySQL, MongoDB, Redis, and MariaDB, along with backup options for supported services.", + }, + ], + }, +}; + +export default function HealthcarePage() { + return ; +} diff --git a/apps/website/app/industries/manufacturing/page.tsx b/apps/website/app/industries/manufacturing/page.tsx new file mode 100644 index 0000000..285f423 --- /dev/null +++ b/apps/website/app/industries/manufacturing/page.tsx @@ -0,0 +1,199 @@ +import { + IndustryPage, + type IndustryPageData, +} from "@/components/industries/IndustryPage"; +import { + Activity, + Boxes, + Factory, + GitBranch, + History, + Workflow, +} from "lucide-react"; +import type { Metadata } from "next"; + +export const metadata: Metadata = { + title: "Manufacturing Technology Deployment Software", + description: + "Use manufacturing technology deployment software to release plant-floor apps, integrations, and internal tools in controlled environments.", + alternates: { + canonical: "https://dokploy.com/industries/manufacturing", + }, +}; + +const data: IndustryPageData = { + hero: { + title: "Manufacturing technology deployment that keeps plants moving", + description: + "Deploy plant-floor apps, integration services, dashboards, and internal tools without relying on unmanaged servers or manual release steps. Dokploy gives manufacturing technology teams a repeatable platform for controlled deployments.", + }, + features: { + heading: "Release operational software without disrupting production teams", + description: + "Manufacturing software supports people, equipment, logistics, and production workflows. Ship changes through a controlled deployment layer with clear environments, monitoring, logs, and rollback options.", + items: [ + { + icon: Factory, + title: "Deploy factory apps without server handoffs", + description: + "Run dashboards, internal tools, APIs, and service interfaces from a platform your team can manage.", + }, + { + icon: Boxes, + title: "Isolate plant, line, and region environments", + description: + "Create projects and environments around sites, regions, product lines, or operational systems.", + }, + { + icon: GitBranch, + title: "Connect Git and Docker workflows", + description: + "Dokploy supports Git providers, Docker, Docker Compose, Nixpacks, Buildpacks, and custom Dockerfiles.", + }, + { + icon: Workflow, + title: "Support integrations and internal APIs", + description: + "Deploy background services, internal APIs, and multi-container systems with Docker Compose, useful for applications that connect operational systems.", + }, + { + icon: Activity, + title: "Monitor workloads across sites", + description: + "Track logs, deployments, server metrics, and application health. Platform teams can support plant software without manually checking every host.", + }, + { + icon: History, + title: "Roll back failed releases quickly", + description: + "Use rollback and deployment history when a release affects an internal tool or operational workflow. Teams can recover faster while they investigate the issue.", + }, + ], + }, + comparison: { + heading: "Modern plant software without unmanaged servers", + description: + "Manufacturing teams often run critical internal software on local servers, one-off scripts, and legacy handoff processes. Dokploy creates a more consistent deployment model without forcing teams into a heavy platform build.", + without: { + title: "Manual plant deployments", + items: [ + "Apps may depend on local server knowledge or individual operators.", + "Release steps can differ by site, team, or vendor.", + "Logs, domains, backups, and rollbacks may be handled manually.", + "Developers may need server access to ship basic changes.", + "Production support becomes harder as internal tools multiply.", + ], + }, + withDokploy: { + title: "Dokploy for manufacturing", + items: [ + "Applications deploy through a controlled platform with familiar workflows.", + "Projects and environments can map to sites, teams, or production systems.", + "Git, Docker, Docker Compose, and database services are supported.", + "Monitoring, logs, backups, and rollback options support day-to-day operations.", + "Remote servers and multi-server management help teams grow across locations.", + ], + }, + }, + workflow: { + heading: "From manufacturing app repository to site-ready release", + description: + "Dokploy helps manufacturing technology teams make releases more repeatable. The same workflow can support a plant dashboard, integration service, internal API, or operations tool.", + steps: [ + { + title: "Create the site environment", + description: + "Set up a project for a plant, operational system, integration service, or regional team. Add development, staging, and production environments as needed.", + flow: "Create project → Add environment → Assign team", + }, + { + title: "Connect the application", + description: + "Connect a Git repository, Docker image, Docker Compose file, or supported build method. Dokploy can automate deployment when approved changes are pushed.", + flow: "Select provider → Choose service → Configure build", + }, + { + title: "Deploy safely", + description: + "Release the app to a controlled environment before production. Teams can review logs, variables, domains, and service settings before promotion.", + flow: "Deploy staging → Validate → Promote", + }, + { + title: "Monitor and recover", + description: + "Watch logs and metrics after deployment, then use rollback options if a release affects an operational workflow. Keep the deployment record tied to the service.", + flow: "Monitor → Alert team → Roll back if needed", + }, + ], + }, + builtFor: { + heading: "Built for plant-floor tools and industrial platforms", + paragraphs: [ + "Dokploy gives manufacturing technology teams a way to standardize application deployment without removing flexibility.", + "Teams can run single-service apps, Docker Compose stacks, databases, and internal APIs through the same platform.", + "Remote servers and multi-server management help teams support workloads across sites or infrastructure zones.", + "Self-hosted and cloud deployment options let organizations choose a model that fits their operational and IT requirements.", + ], + screenshotAlt: + "Dokploy dashboard for a manufacturing operations project with environments for plant-a-staging, plant-a-production, and regional-demo, plus logs, monitoring, domains, and server status", + }, + detailRows: [ + { + area: "Deployment methods", + support: + "Git, Docker, Docker Compose, Nixpacks, Heroku Buildpacks, and custom Dockerfiles", + }, + { + area: "Industrial workflows", + support: + "Site environments, preview releases, webhook deploys, scheduled jobs, and service templates", + }, + { + area: "Access control", + support: "Owner, Admin, and Member roles, with custom Enterprise roles", + }, + { + area: "Infrastructure options", + support: + "Self-hosted Dokploy, Dokploy Cloud, remote servers, and multi-server management", + }, + { + area: "Databases", + support: "PostgreSQL, MySQL, MongoDB, Redis, and MariaDB", + }, + { + area: "Operations", + support: + "Monitoring, logs, backups, rollbacks, domains, MCP, and deployment history", + }, + ], + faqs: { + heading: "Manufacturing technology deployment FAQs", + items: [ + { + question: "What is manufacturing technology deployment?", + answer: + "Manufacturing technology deployment is the process of releasing plant-floor apps, integration services, dashboards, internal tools, and operational software into controlled environments.", + }, + { + question: "Can Dokploy support plant-floor apps?", + answer: + "Yes. Dokploy can deploy web apps, APIs, Docker Compose services, background workers, and databases that support manufacturing operations and internal tooling.", + }, + { + question: "Can teams separate deployments by plant or region?", + answer: + "Yes. Teams can organize projects and environments around sites, regions, product lines, or operational systems. Remote servers and multi-server management can also support distributed infrastructure needs.", + }, + { + question: "Can manufacturing teams self-host Dokploy?", + answer: + "Yes. Dokploy can be self-hosted, and Dokploy Cloud can manage the control plane while applications run on servers connected by your team.", + }, + ], + }, +}; + +export default function ManufacturingPage() { + return ; +} diff --git a/apps/website/app/industries/page.tsx b/apps/website/app/industries/page.tsx new file mode 100644 index 0000000..a020b4d --- /dev/null +++ b/apps/website/app/industries/page.tsx @@ -0,0 +1,140 @@ +import { CallToAction } from "@/components/CallToAction"; +import { Container } from "@/components/Container"; +import AnimatedGridPattern from "@/components/ui/animated-grid-pattern"; +import { Button } from "@/components/ui/button"; +import { + Briefcase, + Factory, + FlaskConical, + HeartPulse, + Landmark, +} from "lucide-react"; +import type { Metadata } from "next"; +import Link from "next/link"; + +export const metadata: Metadata = { + title: "Industries: Deployment Solutions by Sector", + description: + "See how teams in finance, healthcare, manufacturing, pharmaceuticals, and agencies use Dokploy to deploy applications in environments they control.", + alternates: { + canonical: "https://dokploy.com/industries", + }, +}; + +const industries = [ + { + icon: Landmark, + title: "Finance & Banking", + description: + "Deploy internal banking tools, fintech services, and customer-facing apps with governed access, audit logs, and private infrastructure.", + href: "/industries/finance-banking", + }, + { + icon: Briefcase, + title: "Agencies", + description: + "Launch client websites, SaaS products, and campaign apps from one repeatable platform with previews, domains, and whitelabeling.", + href: "/industries/agencies", + }, + { + icon: HeartPulse, + title: "Healthcare", + description: + "Release patient portals, clinical tools, and internal apps in private environments your IT teams can govern and monitor.", + href: "/industries/healthcare", + }, + { + icon: Factory, + title: "Manufacturing", + description: + "Ship plant-floor apps, integrations, and dashboards through controlled environments mapped to sites, lines, and regions.", + href: "/industries/manufacturing", + }, + { + icon: FlaskConical, + title: "Pharmaceuticals", + description: + "Deploy research tools, lab applications, and quality systems with review workflows, rollback options, and enterprise governance.", + href: "/industries/pharmaceuticals", + }, +]; + +export default function IndustriesPage() { + return ( +
+ {/* Hero Section */} +
+ + +
+

+ Deployment solutions for your industry +

+

+ Dokploy gives teams in regulated and fast-moving industries a + governed platform to deploy, review, and operate applications on + infrastructure they control. +

+
+ + +
+
+ +
+ + {/* Industries grid */} +
+ +
+

+ Explore Dokploy by industry +

+

+ The same deployment platform, adapted to the workflows, + governance, and infrastructure requirements of your sector. +

+
+
+ {industries.map((industry) => ( + +
+ +
+

{industry.title}

+

+ {industry.description} +

+ + ))} +
+ +
+ + {/* Final CTA */} + +
+ ); +} diff --git a/apps/website/app/industries/pharmaceuticals/page.tsx b/apps/website/app/industries/pharmaceuticals/page.tsx new file mode 100644 index 0000000..c734376 --- /dev/null +++ b/apps/website/app/industries/pharmaceuticals/page.tsx @@ -0,0 +1,205 @@ +import { + IndustryPage, + type IndustryPageData, +} from "@/components/industries/IndustryPage"; +import { + Database, + Eye, + FlaskConical, + History, + Layers, + ScrollText, +} from "lucide-react"; +import type { Metadata } from "next"; + +export const metadata: Metadata = { + title: "Pharmaceutical Deployment for Regulated Teams", + description: + "Use pharmaceutical deployment software to release research tools, lab apps, and regulated internal platforms in controlled environments.", + alternates: { + canonical: "https://dokploy.com/industries/pharmaceuticals", + }, +}; + +const data: IndustryPageData = { + hero: { + title: "Pharmaceutical deployment software for controlled releases", + description: + "Deploy research tools, lab applications, quality systems, and internal platforms in environments your technology teams can govern. Get a repeatable deployment layer with access control, review workflows, logs, monitoring, and rollback options.", + }, + features: { + heading: "Release pharma software with more control and less manual work", + description: + "Pharmaceutical teams need to support research, quality, digital operations, and internal tools without letting deployments fragment. Dokploy creates a single deployment workflow that teams can adapt to different applications.", + items: [ + { + icon: FlaskConical, + title: "Deploy lab and research tools privately", + description: + "Run internal applications, data tools, dashboards, and service APIs on infrastructure that matches your policy. Choose self-hosted Dokploy or Dokploy Cloud.", + }, + { + icon: ScrollText, + title: "Govern releases with roles and audit logs", + description: + "Use permissions to separate developers, reviewers, and administrators. Enterprise teams can add SSO, custom roles, audit logs, and whitelabeling.", + }, + { + icon: Eye, + title: "Review validation environments before merge", + description: + "Use preview deployments and staging environments to test changes before they reach production users. Review the running service while prepping for release.", + }, + { + icon: Database, + title: "Support databases and service stacks", + description: + "Deploy Docker Compose applications, APIs, background services, and supported databases from the same platform.", + }, + { + icon: Layers, + title: "Keep environments consistent", + description: + "Create repeatable projects for research, quality, lab operations, digital products, and internal platforms.", + }, + { + icon: History, + title: "Restore and roll back critical services", + description: + "Use backups, deployment history, and rollback options when a release needs to be recovered, so teams can respond faster.", + }, + ], + }, + comparison: { + heading: "Regulated software delivery without fragmented infrastructure", + description: + "Pharmaceutical technology environments often include research tools, vendor systems, internal apps, and controlled workflows. Dokploy gives teams one platform for releasing and operating software safely.", + without: { + title: "Fragmented pharma deployments", + items: [ + "Teams may use different servers, scripts, or cloud accounts.", + "Review environments can be inconsistent between applications.", + "Access, logs, backups, and rollback paths may not be standardized.", + "Internal tools become harder to support as teams grow.", + "Deployments depend too heavily on individual infrastructure knowledge.", + "Separate tools means more work to maintain security.", + ], + }, + withDokploy: { + title: "Dokploy for pharmaceutical deployment", + items: [ + "Applications deploy through a repeatable platform.", + "Projects and environments can support research, quality, and digital operations.", + "Git, Docker, Docker Compose, and supported databases are available.", + "Enterprise controls include SSO, custom roles, audit logs, and whitelabeling.", + "Monitoring, logs, backups, and rollbacks support ongoing operations.", + "Create sandboxes where you can deploy safely, even AI-coded software.", + ], + }, + }, + workflow: { + heading: "From pharma software repository to controlled release", + description: + "Pharmaceutical technology teams can move from code to running service through a clear release path. Each step keeps deployment practical for developers and visible to platform owners.", + steps: [ + { + title: "Create the controlled environment", + description: + "Set up a project for a lab tool, research app, quality workflow, or internal platform. Use separate environments for review, validation, staging, and production.", + flow: "Create project → Add environment → Assign roles", + }, + { + title: "Connect the service", + description: + "Connect a Git repository, Docker image, or Docker Compose file. Dokploy supports flexible build types so each app can use the deployment model that fits its stack.", + flow: "Select provider → Configure build → Set variables", + }, + { + title: "Review the running app", + description: + "Deploy changes to preview or staging so reviewers can test the service before production. Logs and deployment history help keep the release path visible.", + flow: "Open preview → Review logs → Approve release", + }, + { + title: "Deploy and operate", + description: + "Release the approved version, monitor health, and use rollback or backup options if the service needs to be restored. Keep operations close to the deployment record.", + flow: "Deploy → Monitor → Restore if needed", + }, + ], + }, + builtFor: { + heading: "Built for R&D, quality, and digital operations teams", + paragraphs: [ + "Dokploy gives pharmaceutical organizations a flexible deployment layer for internal software.", + "Teams can deploy research platforms, lab tooling, dashboards, APIs, and multi-service apps without creating a separate process for every system.", + "The platform supports both self-hosted and cloud control-plane models, which gives infrastructure and compliance stakeholders room to choose how closely the deployment platform should sit inside the organization’s own environment.", + ], + screenshotAlt: + "Dokploy dashboard for a pharmaceutical R&D platform with environments for validation, staging, and production, plus deployments, audit-oriented access controls, monitoring, logs, and database services", + }, + detailRows: [ + { + area: "Deployment methods", + support: + "Git, Docker, Docker Compose, Nixpacks, Heroku Buildpacks, and custom Dockerfiles", + }, + { + area: "Pharma workflows", + support: + "Review environments, staging releases, webhook deploys, templates, and deployment history", + }, + { + area: "Access control", + support: "Owner, Admin, and Member roles, with custom Enterprise roles", + }, + { + area: "Governance options", + support: + "Enterprise SSO, audit logs, whitelabeling, and role-based access control", + }, + { + area: "Databases", + support: "PostgreSQL, MySQL, MongoDB, Redis, and MariaDB", + }, + { + area: "Operations", + support: + "Monitoring, logs, backups, rollbacks, preview deployments, MCP, and remote server management", + }, + ], + faqs: { + heading: "Pharmaceutical deployment software FAQs", + items: [ + { + question: "What is pharmaceutical deployment?", + answer: + "Pharmaceutical deployment is the process of releasing research tools, lab applications, quality workflows, internal platforms, and related services into controlled environments.", + }, + { + question: "How does Dokploy support regulated software teams?", + answer: + "Dokploy supports controlled deployment workflows with projects, environments, permissions, logs, monitoring, backups, and rollback options. Enterprise features add SSO, custom roles, audit logs, and whitelabeling.", + }, + { + question: "Can Dokploy run private pharmaceutical applications?", + answer: + "Yes. Dokploy can be self-hosted, or teams can use Dokploy Cloud while deploying applications on their own connected servers. Both models can support internal and private application deployment.", + }, + { + question: "Does Dokploy support databases for pharma apps?", + answer: + "Yes. Dokploy supports PostgreSQL, MySQL, MongoDB, Redis, and MariaDB, which can be used for internal tools, dashboards, and application services.", + }, + { + question: "Should pharmaceutical teams self-host Dokploy?", + answer: + "Self-hosting is a good fit when teams need to operate the full platform internally. Dokploy Cloud can be a better fit when teams want a managed control plane while keeping application workloads on their own servers.", + }, + ], + }, +}; + +export default function PharmaceuticalsPage() { + return ; +} diff --git a/apps/website/app/sitemap.ts b/apps/website/app/sitemap.ts index d8dbbfa..c5a0103 100644 --- a/apps/website/app/sitemap.ts +++ b/apps/website/app/sitemap.ts @@ -30,6 +30,17 @@ const comparisonPages = [ "/dokploy-vs-portainer", "/dokploy-vs-caprover", "/dokploy-vs-dokku", + "/dokploy-vs-render", + "/dokploy-vs-vercel", +]; + +const industryPages = [ + "/industries", + "/industries/finance-banking", + "/industries/agencies", + "/industries/healthcare", + "/industries/manufacturing", + "/industries/pharmaceuticals", ]; const legalPages = ["/terms-of-service", "/terms", "/privacy"]; @@ -69,6 +80,12 @@ export default async function sitemap(): Promise { changeFrequency: "monthly" as const, priority: 0.6, })), + ...industryPages.map((path) => ({ + url: `${BASE_URL}${path}`, + lastModified: now, + changeFrequency: "monthly" as const, + priority: 0.7, + })), ...legalPages.map((path) => ({ url: `${BASE_URL}${path}`, lastModified: now, diff --git a/apps/website/components/Footer.tsx b/apps/website/components/Footer.tsx index ba06343..cdc4fe3 100644 --- a/apps/website/components/Footer.tsx +++ b/apps/website/components/Footer.tsx @@ -49,6 +49,17 @@ const footerSections = [ }, ], }, + { + title: "Industries", + ariaLabel: "Industry solutions", + links: [ + { href: "/industries/finance-banking", label: "Finance & Banking" }, + { href: "/industries/agencies", label: "Agencies" }, + { href: "/industries/healthcare", label: "Healthcare" }, + { href: "/industries/manufacturing", label: "Manufacturing" }, + { href: "/industries/pharmaceuticals", label: "Pharmaceuticals" }, + ], + }, { title: "Compare & Learn", ariaLabel: "Comparisons and guides", @@ -117,7 +128,7 @@ export function Footer() { {/* Link columns - SEO-friendly grouping */} -
+
{footerSections.map((section) => (