Security from the start
Keep internal services private and provide access to your app over HTTPS. You control who has administrator access.
A server you rent from a hosting provider and control yourself. A free PaaS to deploy on. A fixed server cost you can plan around.
The PaaS brings applications, databases and deployments into one control panel. Your team gets a foundation it can keep building on.
Keep internal services private and provide access to your app over HTTPS. You control who has administrator access.
Review changes in a preview before they reach production. Deploy automatically from Git so your team can spend more time on code.
Store application data in SQL or NoSQL, use caching for quick lookups, and let message brokers distribute background tasks.
Extend the setup with free, self-hosted services for object storage, monitoring and internal tools. The same types of building blocks you know from AWS, Azure and Google Cloud.
Enfikra sets up the foundation. You get a server in your own account with a hosting provider, a free PaaS and the services your application needs.
Fixed rental for your chosen server — with no per-deployment or database-query billing in the PaaS. Capacity and any extras are agreed upfront.
After handover, your team or an external partner handles operations, updates and backups. See what operational responsibility involves
At handover, you review the agreed configuration: access, deployments and your selected services.
The server account and administrator access are yours. Firewall and HTTPS are configured, and the setup is documented.
Your repository connection, automatic deployments and agreed pull-request previews are configured and reviewed with you.
The agreed databases and services are installed with the PaaS. The documentation shows what is running and how to access it.
Usage bills, complex access rules and provider-specific services can make infrastructure harder to manage. Enfikra’s setup gives you more control over cost, access and the services you choose.
From unpredictable bills and platform constraints to a setup you control.
| Your choice of setup | ||
|---|---|---|
| Area | Typical managed cloudTypical drawbacks | With Enfikra’s setupA foundation you control |
| The bill | A final bill that’s hard to predict Usage, traffic and separate services can make the final cost harder to predict. | Fixed server rental. Free PaaS. You pay for the chosen server. The PaaS adds no per-deployment or database-query bill. |
| Access and overview | Time spent navigating consoles and IAM Many services and complex interfaces can take time to navigate and maintain access rules for. | Day-to-day development in one panel Apps, databases and deployments are brought together in the PaaS. You also have administrator access to the server and control who gets access. |
| Choice | Dependent on the provider’s products Provider-specific services and APIs may need changes when you want to move. | A foundation you can take with you Familiar services and access to code, data and configuration reduce dependence on one provider. A move still needs planning. |
| Operations | Operations on the provider’s terms The managed service sets the boundaries for operations and changes. Special requirements need to fit the provider’s product and the agreed service level. | You choose who keeps it running Your team or an external partner takes over ongoing operations after the agreed handover. |
| Managed cloud | With Enfikra |
|---|---|
| The bill | |
| The bill Pricing based on usage, traffic and extra services. | Fixed server rental and a free PaaS. |
| Access and overview | |
| Access and overview Multiple consoles and complex IAM rules. | Apps and deploys in one panel. You control access. |
| Choice | |
| Choice Moving may require changes to your application. | Access to code and data. A move needs planning. |
| Operations | |
| Operations Operations within the provider’s service terms. | Your team or a partner is responsible for operations. |
Inspiration for your setup: a selection of areas and services, not an exhaustive list. The agreed building blocks are configured on your rented server.
Open an area for ideas about what you could use it for.
Use the arrow keys to move between areas and Enter to open one. Tab moves to the next control.
SQL, documents, caching and analytics — or an integrated backend with data, authentication and files.
An SQL database for structured data, relationships and transactions.
Store customers, orders and stock in one structured data foundation for your application.
Read documentation: PostgreSQL (opens in a new tab)A relational SQL database for structured data and transactions.
Run the database for a website, an online shop or an existing application built for MySQL.
Read documentation: MySQL (opens in a new tab)A relational SQL database that supports many MySQL clients and tools.
Store content, customers and orders for applications that support MariaDB. Compatibility with your specific application is checked first.
Read documentation: MariaDB (opens in a new tab)A document database for data with a flexible structure.
Store product catalogs with varied attributes or data from different integrations without forcing everything into one table structure.
Read documentation: MongoDB (opens in a new tab)An in-memory store for caching, sessions and queues.
Reuse frequently read data or track user sessions so the application does not have to retrieve and calculate everything again.
Read documentation: Redis (opens in a new tab)A column-oriented database for analyzing large datasets.
Analyze product usage, log events or order trends without sending every analytical query to the application’s primary database.
Read documentation: ClickHouse (opens in a new tab)A PostgreSQL-based backend with APIs, authentication, file storage and realtime features.
Build a customer portal with shared data, user accounts and file uploads. Your application must be connected to the services; the self-hosted edition has its own feature and operational scope.
Read documentation: Supabase (opens in a new tab)A backend platform with authentication, databases, file storage and functions for your applications.
Give a mobile application user accounts, data access and image uploads without building every core feature from scratch. Integration and operations are planned for your application.
Read documentation: Appwrite (opens in a new tab)Bring code and team tools together, run builds and tests, and connect your systems.
A development platform for Git repositories, code reviews and automated pipelines.
Bring code, merge requests, tests and builds together on your own installation. Pipelines and runners are configured for your workflow.
Read documentation: GitLab (opens in a new tab)A visual tool for connecting APIs and automating workflows.
Move form submissions into a CRM and send a follow-up, for example. The actual workflows are built for your needs.
Read documentation: n8n (opens in a new tab)An automation server for building, testing and delivering software through pipelines.
Run tests and build a container when code changes, for example. Pipelines, agents and connections to your other tools are configured as needed.
Read documentation: Jenkins (opens in a new tab)A low-code tool for building internal interfaces over databases and APIs.
Build an order panel for support or a tool for editing product data. The actual interface and data access are built around your workflow.
Read documentation: Appsmith (opens in a new tab)A self-hosted runner that executes jobs from your GitHub Actions workflows.
Run builds and tests on hardware you control while keeping your existing GitHub workflows. Repositories and job coordination still remain on GitHub.
Read documentation: GitHub Actions Runner (opens in a new tab)A project tool for tasks, issues, priorities and planning your team’s work.
Track bugs, upcoming features and work in progress in a shared workspace on your own installation.
Read documentation: Plane (opens in a new tab)A visual automation tool with connectors between different applications.
Let events in one system trigger actions in another and reduce repetitive manual entry.
Read documentation: Activepieces (opens in a new tab)A shared start page with shortcuts to your web applications and internal tools.
Bring deployments, CRM, documents and dashboards together so new colleagues know where to start. Sign-in and permissions remain managed by the services themselves.
Read documentation: Heimdall (opens in a new tab)Track system health and understand business data and traffic on your website.
Monitors whether your websites and services are available.
Receive an alert when a service stops responding, rather than hearing about it from a customer first.
Read documentation: Uptime Kuma (opens in a new tab)Dashboards that bring together metrics from your data sources.
Track response times and server load, for example. Data sources and alerts are agreed and connected to your setup.
Read documentation: Grafana (opens in a new tab)A tool for querying data and building reports and dashboards.
Give sales and management an overview of orders and revenue without circulating new spreadsheets every week. Data sources and access need to be connected and scoped.
Read documentation: Metabase (opens in a new tab)Web analytics showing visits, traffic sources and events on your website.
See where visitors come from and which pages and actions they use. Your website is connected to the self-hosted installation.
Read documentation: Umami (opens in a new tab)Store and share files, organize team knowledge, and handle documents and backups.
A platform for syncing, sharing and collaborating on files.
Give the team access to shared documents on your own server, with users and sharing permissions.
Read documentation: Nextcloud (opens in a new tab)An object store with an S3-compatible API, built for self-hosting.
Store uploads, images and documents through a familiar API. Capacity and any replication are sized for the workload.
Read documentation: Garage (opens in a new tab)A backup tool with scheduling and encryption.
Copy agreed files to separate storage. Database consistency and restore testing need planning; a backup does not replace an operational owner.
Read documentation: Duplicati (opens in a new tab)A document archive that can recognize text in scanned documents and organize them with tags.
Make supplier invoices and receipts searchable so the team can find documents without browsing folders and filenames.
Read documentation: Paperless-ngx (opens in a new tab)A shared knowledge base that organizes documentation into books, chapters and pages.
Bring onboarding, operating instructions and internal processes together so the team can find answers without searching old chats.
Read documentation: BookStack (opens in a new tab)A tool for preparing documents and collecting electronic signatures.
Send proposals or onboarding documents for signature without receiving printed and scanned PDFs back. Features and integration are chosen for the task.
Read documentation: DocuSeal (opens in a new tab)Centralize sign-in, manage team passwords and control sensitive application settings.
An identity provider for shared sign-in across your services.
Centralize sign-in and access policies so each internal app does not need separate user management.
Read documentation: Authentik (opens in a new tab)A self-hosted password-management server with Bitwarden-compatible clients.
Give the team a shared place for work logins so passwords do not live in spreadsheets or chat messages.
Read documentation: Vaultwarden (opens in a new tab)A central place to manage sensitive application configuration and credentials.
Distribute the right settings to development and production rather than sharing them in chat or scattering them across projects. Application integration and access are agreed separately.
Read documentation: Infisical (opens in a new tab)Identity and access management with single sign-on and standards such as OpenID Connect and SAML.
Connect applications to the same identity and manage users and roles centrally.
Read documentation: Keycloak (opens in a new tab)Connect background work, system notifications and conversations with your team or customers.
A message broker that routes messages between applications and workers.
Queue emails or imports for workers to process in the background. Worker code and integration are built separately.
Read documentation: RabbitMQ (opens in a new tab)A notification service that applications and scripts can publish to over HTTP.
Receive a phone notification when an import finishes, a backup job fails or a new case needs attention. Events are connected to your systems.
Read documentation: ntfy (opens in a new tab)A platform for team communication with channels and messages.
Bring incident discussions and project channels onto your own server so the history sits alongside your other tools.
Read documentation: Mattermost (opens in a new tab)A shared inbox for customer conversations with support for website chat.
Let colleagues follow up on customer enquiries from one inbox and see the conversation history. Channels and integrations are configured as needed.
Read documentation: Chatwoot (opens in a new tab)Candidate services, not a bundled package. Services, capacity and licensing are clarified before setup. Application integration and data migration are agreed separately. You can add more services yourself afterwards.
How your setup is delivered. Each step has a concrete outcome before the work moves on.
You show what runs today and what the new setup needs to do. Enfikra brings requirements, boundaries and acceptance criteria into a shared agreement.
When the setup is ready, your team tries it together with Enfikra. Questions and necessary adjustments are addressed before the solution is accepted.
The setup is reviewed with the person or partner taking over. At handover, you know where the documentation is and who to contact when something needs action.
You rent the server from a hosting provider. You control the server account, administrator access, data and configuration. You pay a fixed server rental price directly to the hosting provider.
No. You rent the server from the hosting provider with no minimum term. Setup is paid once, and the rental fee is paid directly to the provider.
Setup has a separate, agreed one-time fee. You pay the fixed rental fee to the hosting provider. After handover, your technical owner is responsible for operations, updates and backups unless agreed otherwise.
The server is chosen for the agreed requirements. As those change, you can choose more capacity or plan a move. A larger server and any additional work are scoped separately.
Yes. Access to your code, data and configuration gives you a starting point for a move. The migration still needs planning, particularly for databases, DNS and any downtime.
Tell us about your application, data and current hosting. That turns your needs into a concrete setup with a clear price and responsibilities.