Deploying a private server requires hands-on developer expertise. You will need to create infrastructure accounts, configure databases, manage DNS records, and handle environment variables. If you or your organisation does not have a developer on the team, this process is not for you.
Not a developer? Join one of our public servers instead — no setup required, just sign up and start working.
Your deployment control centre.
The Dev Server is a special environment inside LogbookOS where developers create and configure dedicated private servers. The entire process is guided and automated — but requires real technical knowledge to complete.
Automated Setup
The server creation process is fully automated. You provide the credentials, we deploy the instance.
Full Isolation
Your own database, auth system, usage ledger, and deployment. No shared infrastructure.
Choose Your Mode
Install LogbookOS in Work, Edu, or DIY mode. Each server runs one operating mode.
Two reasons to go private.
A private server is not for everyone. Our public servers handle most use cases. Choose a private deployment only when you genuinely need one of these:
From application to live server.
The deployment follows a structured, step-by-step process. Each phase must be completed before moving to the next. The entire workflow is guided through the Dev Server interface.
Phase 1 ... Register & apply for access
Phase 2 ... Create infrastructure accounts
Phase 3 ... Create server instance
Phase 4 ... Configure environment variables
Phase 5 ... Connect domain & DNS
Phase 6 ... Verification & go-live
status: all phases guided through the Dev Server UI
Register & Apply for Access
Application review: 1–3 business days
Access to the Dev Server is not automatic. You submit an application and our team reviews it before granting access.
Create Infrastructure Accounts
Your accounts, your payments, your responsibility
Before we can deploy your server, you need to create accounts on the required third-party services. These are your own accounts with your own billing. We never access or manage them beyond what’s needed for deployment.
Create Your Server Instance
Choose your operating mode: Work, Edu, or DIY
With all infrastructure accounts ready, use the Dev Server’s guided wizard to create a new server instance. You’ll choose which LogbookOS operating mode to install.
Configure Environment Variables
Connect all services to your server
Enter the credentials and configuration keys from all the accounts you created in Phase 2. This connects your database, storage, AI providers, and other services to your new server instance.
DATABASE_URL ........ Render PostgreSQL
CLOUDFLARE_R2_* ...... R2 bucket credentials
CLOUDFLARE_STREAM_* .... Stream service keys
OPENAI_API_KEY ........ Whisper + GPT access
ANTHROPIC_API_KEY ...... Claude AI access
CUSTOM_DOMAIN .......... your.domain.com
status: all variables entered via guided form
Connect Domain & DNS
DNS propagation: 1–48 hours
Add your chosen domain to the server configuration. You’ll receive the IP address and DNS records that you need to add to your domain registrar or DNS provider.
Verification & Go-Live
Our team checks everything before handover
Once the domain is connected and the server is online, our team performs a stability and functionality check. We verify that all services are connected correctly, the database is responding, and the platform is fully operational.
Application-level access only.
We provide the LogbookOS software. Everything else — the front page, legal pages, analytics, and public presentation — is your responsibility.
With full control comes full responsibility.
Running a private server means you are responsible for your data, your compliance, and your infrastructure accounts. This is not optional — it’s a core part of the agreement.
We can handle it for you — at extra cost.
If your team cannot complete the deployment independently, we offer professional setup support. The cost is clearly defined during the server creation process.
Self-Service
Managed Setup
Deployment Checklist
| Phase | Step | Details |
|---|---|---|
| 1 | Register on DIY Server | diy.logbookos.com → create account |
| 1 | Register on Dev Server | Developer account access |
| 1 | Submit application | Details + use case + bio → 1–3 day review |
| 2 | Create Render account | PostgreSQL database |
| 2 | Create Cloudflare account | R2 bucket + Stream service |
| 2 | Create OpenAI account | API key for Whisper + GPT |
| 2 | Create Anthropic account | API key for Claude |
| 2 | Get a domain | Subdomain or new domain |
| 3 | Create server instance | Choose Work / Edu / DIY mode |
| 4 | Enter environment variables | All credentials from Phase 2 |
| 5 | Connect domain & DNS | Add DNS records → wait 1–48h |
| 6 | Verification & go-live | Team check → access granted |
Dev is how you deploy your own server.
The public servers are ready to use today. The Dev Server is how you create a private instance when your organisation needs full control.
LogbookOS is a SaaS platform. Private server deployment provides a licensed instance of the LogbookOS software. The license includes the application software and ongoing platform updates. Infrastructure costs (hosting, storage, AI APIs, domain) are the responsibility of the deploying organisation. All pricing details are shown during the server creation process. Operated by Em.Skoulikaris LLC.
Ready to deploy?
Start with the application.
Register on the DIY Server, access the Dev Server, submit your application, and start the deployment process. Full documentation is available inside the platform.
Developer expertise required · Application review: 1–3 business days