This FAQ answers the most common questions from prospects and customers about the Caelum appliance (edited by GaLiLo). Answers are deliberately short and factual. For detailed procedures, see the installation guide and the administration guide.
The product in brief#
What is Caelum?#
Caelum is a NAS appliance from the personal GaLiLo project. It provides SMB/NFS shares, archiving to a qualified S3 target and incremental copy from SMB. It is distributed as an ISO; validate your platform and sizing in a pilot.
How is it different from a regular NAS?#
Caelum combines local storage, S3 archiving with stubs at the original path and incremental SMB migration. These features have protocol, recall and permissions-fidelity limits. Evaluate them against your requirements without assuming exclusivity over other NAS products.
Is Caelum a sovereign cloud?#
No: you choose the appliance infrastructure and its object-storage target. Data residency depends on that choice and the contracts. Recall is on demand, not guaranteed to be instant; qualify the backend before use.
How is it different from a regular cloud gateway?#
Archiving replaces eligible files with stubs at their original paths. Tasks resolve their scope and destination; first-run simulation is an overridable default. Recall depends on the protocol, active modules and S3 availability.
Sovereignty and data#
Where does my data stay?#
Local files reside on your infrastructure; archives reside on the configured object-storage target. Check residency and recipients separately for files, AI, activation and telemetry. Choosing Caelum alone does not guarantee French data residency.
Does Caelum "phone home"?#
Token signatures are checked locally. This does not remove exchanges for activation, renewal or the assistant. Telemetry is enabled by default, on the basis of legitimate interest in tracking versions so security fixes can be shipped. The data are pseudonymous and linked to the licence. Sending is daily and can be disabled in System › Privacy. Details are in the portal and product notice.
Is my data subject to the Cloud Act?#
Server location alone does not exclude the application of foreign law. Review operators, contracting entities, subprocessors, regions and transfer safeguards for each data flow. Caelum alone is not a legal guarantee.
Security and resilience#
How does Caelum protect against ransomware and mistakes?#
SMB veto filtering matches names and extensions; it does not detect every attack. Snapshots can restore an earlier state when a suitable recovery point is available, alongside independent backups.
Known limitation in 0.65.9 — T-236: the veto also affects legitimate files such as .lock and .enc. It can reject creation or make existing files invisible and unreadable over SMB, without deleting them from disk. A fix is planned for 0.65.10; it is not delivered in the version described.
ZFS snapshots are read-only, subject to administrative permissions and retention. They are neither a WORM guarantee nor an offline backup.
Recovery requires a point created before the incident. For archived files, follow the restoration and catalog replay limitations of the installed version.
Alerting and logging integrations must be described in terms of the events, formats and destinations actually tested.
How do I expose Windows "Previous Versions"?#
Explicitly configure and verify snapshots and retention, then test the Windows workflow on your files. An archived-file restoration workflow was tested, but not every case is qualified. Follow the restoration and catalog replay procedure; do not restart the service before replay completes. No universal retained-snapshot count is claimed here.
Is there an access audit log?#
The configuration provides Samba events. Before relying on them for investigation, define and test the expected events, formats and destinations. This does not guarantee complete SIEM integration or regulatory compliance.
Which high-availability modes does Caelum offer?#
Caelum 0.65.9 provides unqualified beta modes; validation outside production is necessary.
- Shared storage: Pacemaker orchestrates the primary pool, shares and VIP. The setup script includes SCSI/VMware fencing, but the wizard cannot configure it. The campaign does not qualify RPO/RTO or transparent session continuity.
- Replication: asynchronous ZFS snapshots with manual promotion. RPO is the age of the last successfully received snapshot and can exceed the configured interval. Local promotion precedes the remote demotion request; demotion failure does not undo promotion. Isolate the peer before promotion: acknowledgements do not fence it.
The S3 secret can be transported and re-encrypted when the channel supports it; re-entry is needed if transfer or adoption fails. Check secrets and AD identities on the recovery node. The campaign contains no two-node Caelum cluster acceptance test.
Are communications encrypted?#
The administration interface is served over HTTPS. The certificate is self-signed by default; you can install your own.
Compatibility#
Which sharing protocols are supported?#
SMB (Windows shares) and NFS (Unix/Linux), with a per-share read-only option.
Does Caelum integrate with Active Directory?#
Active Directory integration was tested in an SMB/NFS scenario. Distinguish the historical model from “applied permissions” mode: their interaction with system permissions differs. NFS AUTH_SYS is not equivalent to rich NTFS ACLs. Before enabling cross-protocol access, test owner, DENY, inheritance, nested groups and resolved identities. Campaign case T-243 concerns the tested 0.65.7 scenario, not every 0.65.9 mode.
What can I install it on?#
The documented test environment uses Proxmox. Validate the intended platform, drivers and resources for your workload before deployment. An advertised compatibility list is not a qualification matrix.
What throughput to the object storage should I plan for?#
Measure first access, sustained throughput, memory and concurrent reads against your target with your applications. Recall depends on the network and S3 availability. The historical slow-target NFS read issue was fixed in 0.65.7; test mount options and residual cases on the installed version.
Which object storage backends are compatible?#
An S3-compatible API does not guarantee identical behavior. Qualify the chosen target for range reads, preconditions, purge and versioning; consult the provider’s dated offer for costs and retention.
Can I use a SAN / iSCSI array?#
SAN connectivity, authentication and path redundancy require dedicated validation on your hardware. This FAQ does not claim general qualification of CHAP/MPIO or iSCSI configurations.
Does Caelum manage several storage pools?#
Recovery coverage depends on the mode. Shared-storage HA covers the primary pool. For replication, check the datasets and jobs actually configured: additional pools are neither universally excluded nor automatically all protected.
Does the appliance appear in the Windows network neighborhood?#
Check network discovery with your client versions and network rules. This overview does not guarantee automatic discovery on every client.
Migrating from an existing NAS#
Can Caelum migrate my old NAS?#
The verified workflow copies data incrementally from SMB and can be rerun. A completed status can still carry copy or permissions warnings: review the report. Permission fidelity may be partial; the described code does not deliver an independent, exhaustive post-copy hash pass. Plan explicit data and access checks before cutover.
Will I lose my Windows permissions when migrating?#
Check ACL reproduction rather than assuming exact fidelity. Validate owner, inheritance, DENY, nested groups and identities on representative samples. A successful SMB test does not establish equivalent NFS AUTH_SYS permissions.
Optional AI assistant#
What is the Caelum AI assistant?#
Two modes, both disabled by default, each requiring explicit activation by the administrator. The first uses a Mistral key provided by GaLiLo, in particular for proofs of concept: once enabled, content sent to the assistant is transmitted to Mistral AI. The second is BYOK (your own key, an OpenAI-compatible endpoint, for example Mistral, OVH AI Endpoints or local Ollama): the key is stored encrypted and is not logged. The BYOK screen is planned for release 0.65.10; it is not delivered in the version described. The website does not process this content. The api.galilo.io/ai gateway is disabled by default.
Does the AI see the content of my files?#
The exact scope of transmitted messages and tools must be documented after an audit. The gateway relays message payloads; the verified corpus does not establish that file content can never be included. Do not enter confidential information before checking this scope.
Where are my questions to the assistant processed?#
Once the GaLiLo-provided Mistral key mode is activated, content sent to the assistant is transmitted to Mistral AI. The place of that processing and how long the content is kept are not stated here. BYOK, when its screen is delivered, will send content to the endpoint configured by the administrator. French residency, overall compliance or exclusion of foreign law is not inferred from the code alone.
Licensing and trial#
What license editions exist?#
The validator recognizes Free, Trial, Production and NFR tokens and checks their Ed25519 signatures locally. Features and expiry depend on the issued token and validated terms. The autonomous trial is separate, not itself a signed token; type names do not establish a commercial offer or perpetual free use.
How does the trial work?#
The autonomous trial starts locally for 30 days, without Internet or prior registration. Its displayed “1 TB” cap is enforced as 1024 GiB (1 TiB) of allocated volume quotas, not as a continuous measurement of all physical or S3 bytes. Explicit quotas are required when creating or changing volumes. Local persistent state and a clock check govern the trial, but are not an inviolable barrier. On expiry, some API mutations are blocked, with exceptions; this does not establish a general read-only transition for SMB/NFS shares. Online services and pilot terms are separate.
Is the license verified online?#
The token’s signature is checked locally. Activation, renewal and the assistant are separate workflows that can use the network. This does not mean every service works without Internet; prepare isolated operation according to applicable entitlements and terms.
Updates and support#
How are appliances updated?#
Stable and beta channels are available. On a compiled appliance, a local package can be installed without the appliance downloading it; this does not make online services available offline. Returning to a code version differs from restoring data, which discards writes made after the selected recovery point. Check the confirmation and procedure before restoring.
Is there a pre-release (beta) channel?#
Yes. A beta channel lets testers evaluate new versions early. The stable channel remains recommended for production.