Krayin hosting, on a server we run.
Krayin, the open source Laravel CRM, deploys as a one-click template with its MySQL database and schema installed onto a dedicated server Selfhost.dev provisions, secures and runs, across six locations on three continents. An 8 GB machine in Europe costs $0.03/hr, about $23 a month if you leave it running, and its Laravel encryption key is yours alone.
One click. Two containers. The template deploys in about 15 minutes.
no signup
+$5.00 added at signup · deployment choice preserved · no card
Price the server before you commit to anything: the calculator takes no signup, and the template deploys in about 15 minutes.
- Krayin with MySQL 8.4 bundled
- A European 8 GB server is $0.03/hr, about $23 a month if you leave it running
- Custom domain and HTTPS included
- 6 server locations on 3 continents
What Krayin hosting actually means
Someone else owns the machine.
You own the database.
What it is. Krayin is an open source CRM built on Laravel and Vue, covering leads, contacts, organizations, quotes and deal pipelines. Krayin hosting means that application running on a server we provision and maintain, with its MySQL database on the same machine and nothing metered above the server itself.
Who it is for. Small and mid-sized sales teams who want their customer records in a database they control, and who do not want to be the person who patches the box. It suits a team that has outgrown a spreadsheet and does not want a per-seat subscription.
When to use it. When the per-user bill on a hosted CRM has started to scale faster than the team, or when the customer data has to sit in a specific place for a policy reason. It is also the cheapest way to put a real CRM in front of a team that is still deciding whether it wants one, because you pay by the hour.
Krayin hosting requirements
What Krayin needs, and what we already provide.
| What Krayin needs | This deployment |
|---|---|
| Runtime | Laravel on php-fpm behind nginx |
| Database | MySQL 8.4.11, bundled on the project server |
| Containers | 2 |
| Memory | 8 GB recommended, classed heavy. Krayin's own documented minimum is 3 GB for Krayin alone, which is the figure our CRM comparison reports. Ours is 8 GB because this is a two-container deployment, Krayin plus its MySQL on the same machine, and the first boot that installs the schema is the memory peak rather than steady state |
| Architecture | x86 only. The upstream image publishes no arm64 build |
| Scheduler | Not started in v1, so inbound IMAP fetching does not run |
| Outbound email | Configured inside Krayin after it is running |
| What Selfhost.dev provides | Detail |
|---|---|
| Regions | 6 locations on 3 continents |
| TLS | Let's Encrypt per hostname, renewed for you |
| Custom domain | One customer-owned domain per resource |
| Backups | Optional, whole VM, daily, last 7 kept, +20% of the server price |
| Metrics | Server CPU and memory, plus a 60 second health check |
| Version policy | Pinned to an exact tag, never a floating one |
| MCP | Covered. Deploy and manage this template from Claude, Cursor or any MCP client |
Specifications current as of September 2026. The x86 restriction carries no price penalty at this size: the cheapest 8 GB machine we sell is cx33 at $0.03/hr, which is x86 anyway, and the ARM equivalent cax21 is $0.04/hr.
What's in the Krayin deployment
Two containers, two volumes, one key that is yours alone.
Selfhost.dev pins every image to an exact tag, so your version never moves until you ask for it.
| Component | Version | What it does |
|---|---|---|
| Krayin CRM | webkul/krayin:2.2.0 | The application, nginx and php-fpm under supervisord |
| MySQL | 8.4.11 | The database, on the same project server |
| Persistent volumes | krayin-storage, mysql-data | Uploads and database files survive a container restart |
Laravel APP_KEY | generated per deployment | 32 bytes, persisted, so a redeploy does not invalidate sessions |
Specifications current as of September 2026. Two containers, not one: the web container plus a MySQL sidecar on a per-service DNS name.
What we set up for you
Three things the upstream image gets wrong, fixed before it serves.
This is the anti-DIY argument, and on Krayin it is unusually strong, because three things here are ours and not upstream's.
| What the upstream image does | What Selfhost.dev does instead |
|---|---|
| Installs Krayin at build time into a MySQL baked inside the image, and runs no migration against an external database | Our first-boot bootstrap reads state from your own database, and where the users table is absent it installs the schema, finishing before nginx ever serves a request |
Ships a seeded [email protected] | Rotated to your own email address and password before the first boot, so it never comes up on a documented default |
Bakes one APP_KEY shared by every deployment of that tag | A 32-byte key generated for your deployment and persisted, so sessions and encrypted columns are not interchangeable with anyone else's |
Also wired without you asking: APP_URL, APP_ENV=production, APP_DEBUG=false and the full DB_* set. TLS is a Let's Encrypt certificate per hostname. The firewall is default-deny with only 22, 80 and 443 open. Each customer gets one VM, and services get per-service DNS names so two stacks cannot cross-resolve. No template ever boots on a documented default password: where seeding fails, the instance boots locked rather than open.
How to self host Krayin in four steps
From zero to live.
No server to set up.
Four steps. Two containers, and the schema installs itself before Krayin first answers.
1. Choose Krayin
Open the Krayin template in the console, pick a server size and one of six locations, then submit. The recommended size is 8 GB, and the machine has to be x86, which the console resolves for you.
2. Set access
Krayin authenticates by email address, so the administrator sign-in is the email you set at deploy time, with the password you set alongside it.
3. Let it start
The template deploys in about 15 minutes. The console tracks provisioning, installs the schema, gives the app a generated HTTPS address and shows server CPU and memory after launch.
4. Import and start selling
Sign in with the email address and password you set at deploy time. Bring your contact list in through Settings, Data Transfer, then build your first quote from a lead.
What we run, and what you run
The honest split.
| Selfhost.dev runs | You run |
|---|---|
| The server, its operating system and the firewall | Krayin itself: users, roles, pipelines and email settings |
| Provisioning, the first boot and the schema install | Your data, your imports and your exports |
| TLS certificates and the custom domain routing | Which Webkul modules, if any, you buy |
| Server CPU and memory metrics, and a 60 second health check | Deciding when to move to a bigger machine |
| Optional whole-VM backups | Taking your own database dumps if you want a second copy |
We manage infrastructure, not application administration. There is no fully managed Krayin administration here, and we would rather say so than let you find out later.
What an 8 GB server handles
We will not invent a user count. Here is what the machine actually has left.
An 8 GB server has 6,656 MB available after the host reserve. Krayin runs as one web container plus MySQL, which leaves real headroom: the same machine fits three heavy applications and one light one, or any lighter mix. So a team running Krayin on its own 8 GB box is not near the ceiling, and the same server can carry a second and third application from the catalog before the five-workload cap binds.
What we will not claim is how many contacts, leads or concurrent users Krayin itself will serve, because we have not measured it and neither has anyone publishing a number for it. Krayin's own configured ceiling in this deployment is one web container and no scheduler.
Krayin hosting cost
Hourly, so a CRM you are still evaluating costs nothing overnight.
You pay for the server and nothing else. An 8 GB machine in Europe is $0.03/hr, about $23 a month if you leave it running, billed hourly against prepaid credits, and stopping it stops the bill.
| Machine | Location | Cores | RAM | Disk | Hourly | Monthly at 730 hrs |
|---|---|---|---|---|---|---|
cx33 (recommended) | Europe | 4 | 8 GB | 80 GB | $0.03/hr | $23.36 |
cx43 | Europe | 8 | 16 GB | 160 GB | $0.06/hr | $43.22 |
cpx31 | Singapore | 4 | 8 GB | 160 GB | $0.12/hr | $90.08 |
ccx13 | US, Ashburn or Hillsboro | 2 dedicated | 8 GB | 80 GB | $0.16/hr | $119.28 |
Monthly figures are computed at 730 hours. One machine type in one location per row. cx33 is sold in Europe only, which is why the US and Singapore rows are different machines rather than the same one at a different price. Krayin cannot run on our ARM sizes, so the ARM row other pages carry is absent here.
| Item | Cost |
|---|---|
| The Krayin template | $0 |
| The bundled MySQL database | $0 |
| HTTPS and one custom domain | $0 |
| Users, seats or agents | $0 |
| Bandwidth | $0 |
| Backups | Optional, +20% of the server price |
No bandwidth charges: you pay for the server, traffic is included. A template project bills exactly two things, compute and backup if you enabled it. There is no egress component registered for a project and no traffic metering is collected, so there is nothing that could be billed. Railway and Render both meter egress. If the credit balance reaches zero, welcome-credit-only servers are deleted immediately. Accounts with a card on file or a past top-up get a 24 hour pause and email warning first, and adding credit during that window restarts the project. Backups sit next to this sentence rather than three sections away because they live with the server, and prepaid credit means there is no invoice to be surprised by. The calculator carries the full ladder and every region.
What we promise about the machine
Five things, all code-verified.
- Every service is health-checked every 60 seconds.
- A stalled deploy is retried automatically, not abandoned.
- A deploy is never reported done until the URL actually answers.
- Retrying a create never leaves you paying for two copies.
- Your version never moves on its own.
The template deploys in about 15 minutes, which is the platform's own budget rather than an estimate: a pull of about 770 MB, a MySQL initialisation, then the schema install runs to completion before nginx starts serving. It is one of the slower templates we run, and we would rather say so than have you watch a spinner.
Tell us the size of your sales team
Send us how many people will use Krayin and roughly how many contacts you are bringing across, and we will send back the server size, the monthly cost and whether the import needs splitting. No newsletter, and no sales sequence. One reply with the numbers.
What Webkul sells instead of Krayin hosting
They sell the installation. We sell the running machine.
Webkul, the company behind Krayin, publishes no hosted Krayin you can subscribe to. What its store sells is one-time work: setup plans on the customer's own cloud that are quoted rather than priced, a starter pack and a multi-tenant module. None of it includes the cloud bill the software then runs on.
| What Webkul sells | Price | Recurring? | What it covers |
|---|---|---|---|
| Cloudkul Silver, AWS setup | Quote on request | One time | Setup on AWS, with a support period |
| Cloudkul Gold, AWS setup | Quote on request | One time | The same setup with a longer support period |
| Krayin Starter Pack | $499.00 | One time | Installation, consultancy and basic training |
| Multi Tenant SaaS module | $1,799.00 | One time | Multiple tenant instances, domains and user permissions |
Prices from store.webkul.com, checked 16 September 2026, USD view.
There is no crossover, and that is the honest version. We are not going to claim to be cheaper: the two things are different purchases. Their fee buys a day of somebody's attention and then leaves you owning a server: the patching, the backups, the cloud invoice that their price does not include, and the upgrades. Ours is the running machine, for as long as you run it, with the install already done.
Krayin hosting vs Zoho CRM
One bill grows with the team. The other grows with the machine.
Zoho CRM is the subscription a Krayin evaluator is most often leaving: the same buyer, small and mid-sized sales teams, and a free edition capped at three users. This section argues on the shape of the bill, not its size, because Zoho prices per user in your local currency and we only quote dollars we can check.
| Zoho CRM | Krayin on Selfhost.dev | |
|---|---|---|
| What the bill scales with | Every user you add | The server, and only when you change it |
| 3 users | Free edition, then per user | A European 8 GB machine, $23.36 a month |
| 10 users | Per user, ten times | The same machine, the same $23.36 |
| 25 users | Per user, twenty-five times | The same machine, or the 16 GB one at $43.22 |
| Where the records live | Zoho's tenancy | A MySQL database on a server you can dump |
| Pausing it | Cancel the subscription | Stop the machine, stop paying by the hour |
When a hosted CRM is the better choice
Buy the subscription if you want somebody else accountable for the application itself and not just the machine it runs on. We provision, secure and run the server, and we install the schema and seed the administrator, but the roles, the pipelines, the email configuration and the upgrade decisions are yours. A hosted CRM with a support contract answers "why did this workflow stop" in a way infrastructure management does not. And if the plan is to run Krayin as a CRM for your own clients, each on their own domain, multi-tenancy is a licence-gated module Webkul sells separately, and no amount of hosting produces it. We can run the module once you own it. We cannot substitute for it.
The line that carries this section: adding your fourth salesperson changes a per-user bill and does not change ours. That is the whole of bill variance, measured against per-user pricing.
Krayin hosting limitations
App-specific first, because the first one is about a feature on the settings screen.
- Inbound email fetching does not run. Krayin registers exactly one scheduled task,
inbound-emails:process, and this deployment starts no Laravel scheduler, so the IMAP settings screen is present in the interface and will not pull mail. Krayin 2.1.0 introduced IMAP as a headline feature, so this is worth knowing before you plan around it. Leads, contacts, deals, activities, outbound mail and event-driven workflows are unaffected. - x86 servers only. The upstream image publishes a single
linux/amd64manifest, so creating this template on an ARM project is refused. At the recommended 8 GB the cheapest machine is x86 anyway, so the restriction does not change the bill. - One web container. No horizontal scaling of the application in v1.
- Multi-tenancy needs a Webkul module. Covered in the comparison above.
- The first boot takes about 15 minutes while the schema installs, far longer than the container start.
- Custom field import is not available at this version. Import and export of custom attributes arrived in Krayin 2.2.5 and this deployment is pinned below it. See the migration section.
- We manage the server, not the application. There is no auto-restart of a crashed service, the health check is observational, and application administration stays with you.
Krayin backup and restore
Two copies, and a way out that does not need us.
Optional backups protect the whole project VM, Krayin and MySQL together, and they cost 20% of the server price. Because the database sits on the same machine as the application, one VM backup is a consistent pair rather than two things that might disagree.
Your own copy, at any time
Krayin's data is a MySQL database plus the krayin-storage volume, so a mysqldump and a copy of that volume is a complete, portable snapshot that restores onto any Krayin of the same version, here or anywhere else. Add your own SSH key to the project server and you have a root shell to take it from.
Leaving is a dump and a file copy
Nothing about the format is ours. The database is ordinary MySQL and the uploads are ordinary files, so the same two artefacts that back you up are the ones you would leave with.
Backups do not survive zero-balance destruction because they live with the server. A welcome-credit-only project is deleted immediately at zero; funded accounts get a 24 hour pause and can restart after adding credit. Keep your own dump if the data matters.
Migrating to Krayin with Data Transfer
Your existing contact list, in a file Krayin already reads.
Krayin ships a bulk importer, reached at Settings, then Data Transfer, then Create Import. It is present at this deployment's version, and it does not need us to build anything.
| Detail | |
|---|---|
| File formats | CSV and Excel |
| What it imports | Persons, Leads and Products |
| Getting the shape right | Download Sample returns a correctly formatted template |
| Checking first | Validate Data tests the file before anything is written, and you choose whether an error stops the import or skips the row |
| Large files | A background mode imports without holding your session open |
Scoped deliberately to standard fields. Import and export of custom attributes for Leads and Persons, and Google Contacts export with duplicate detection, both arrived in Krayin 2.2.5, which is above this deployment's pin. Do not plan on custom fields until the template moves.
Frequently asked questions
Is Krayin available as a one-click template?
How much does Krayin hosting cost?
How do I sign in to Krayin?
Can I use my own domain for Krayin?
What does Selfhost.dev manage for this deployment?
Can I run Krayin on an ARM server?
Does inbound email work in this Krayin deployment?
Can I import my existing contacts into Krayin?
About Selfhost.dev
Selfhost.dev is a managed infrastructure product from Swatantra Cloud Systems Pvt Ltd. We run fully managed PostgreSQL, MySQL, Redis, ClickHouse, OpenSearch and Kafka on AWS, plus Projects, a dedicated server you deploy applications onto from GitHub or from 44 one-click configurations. Billing is pay-as-you-go against prepaid credits, with no tiers and no subscriptions.
Best for: Krayin, Twenty CRM, EspoCRM, Odoo and managed PostgreSQL, MySQL, Redis, ClickHouse, OpenSearch and Kafka.