Your Philos server
Overview
Loading…
Keep your apps connected
Share your public server connection code and give each user an activation password. Their devices will appear here after they connect.
Manage access
Choose a device limit for each app password. One-time access activates each device once; permanent access allows an enrolled device to enter its password again.
Published updates
Connected apps check for changes when opened and while in use. Messages update automatically; app downloads need the user’s approval.
Users & devices
Each row is a connected installation. Name devices to identify your users.
| Name | Platform | App version | Last seen | Access | Actions |
|---|
No devices are connected yet. Open Connect apps to get started.
Blocking a device takes effect at its next server check. Previously issued offline approval lasts up to seven days when the server cannot be reached.
Create an app password
These passwords activate app access. They cannot sign in to this owner panel.
One-time and permanent access
A new one-time password allows one activation per device, up to your chosen device limit. Each device stays approved through its saved session. A device that already used this password cannot enter it again, even after moving to another password.
A permanent password allows its enrolled devices to enter the password again without taking extra slots. Blocking a device frees a slot for a different installation; unblocking needs a free slot. Revoking a password prevents new activations.
Older permanent passwords retain unlimited devices. Older one-time passwords still allow only one activation total and are labelled legacy below.
The password can be revealed or copied once after creation. Store it safely before closing its window.
Your app passwords
| Name | Type | Status | Devices used / limit | Expires | Action |
|---|
No app passwords yet. Create one above.
Messages, banner & app defaults
Connected apps receive your published changes on their next check. The banner and defaults need Philos 7.5.0. Existing 7.4.0 apps continue to receive messages.
Current releases
Publish an app update
Publish a complete APK or Windows archive. Users will see the update in connected apps, and the download is checked against its SHA-256 hash.
Android updates must use the same app signing certificate as the installed version. Existing apps need the first server-enabled build before they can receive these update notices.
Connect your apps
Share this public connection code with your users. In Philos, open Settings → Your server, paste the code, and enter the app activation password you have created for them.
The connection code contains only your server address, server ID and public verification key. It does not include passwords.
This server is using a local address. Configure its public HTTPS address before sharing the connection code outside your PC.
Recent activity
Access changes, messages, releases and owner actions recorded by your server.
| Time | Action | Target | Details |
|---|
There is no activity yet.
Change your owner password
Other owner sessions will be signed out. App activation passwords are managed separately.
Back up your server
Download a consistent copy of your users, app passwords, settings and release records. Store it privately.
The database backup does not contain your signing key or uploaded release files. Keep a separate private backup of the server data folder so you can restore the same server identity.