Connect and use Own Infrastructure
Connect a server through SSH/SFTP, review remote source and deploy with recovery controls.
Connection requirements
- A live HTTPS site URL and an SSH hostname reachable on the configured port.
- A restricted SSH user with only the permissions required for this project.
- Private-key authentication is preferred; password authentication is also available.
- Separate, non-nested Project source path and Public web path directories.
- Node.js and npm available for the configured remote build flow.
- The SHA-256 SSH host fingerprint obtained independently from the hosting provider.
Verify the server identity
Use Scan fingerprint, compare the SHA-256 value with the hosting provider and confirm trust only when they match. A changed fingerprint can indicate a rebuilt server or an impersonation attempt and must be investigated before reconnecting.
Connect the server
Choose Own Infrastructure
Open the project's infrastructure settings and select Own Infrastructure as the hosting target.
Enter the target details
Provide a label, live site URL, SSH hostname, port, username, authentication material, Project source path and Public web path.
Scan and approve the fingerprint
Choose Scan fingerprint, verify it outside Aetherion and select the trust confirmation.
Test connection
Aetherion validates SSH, SFTP, the paths and required runtime before credentials are accepted for deployment.
Connect server
Save the verified target. Later changes use Verify & save so an untested configuration cannot silently replace the working target.
Credentials remain server-side
Passwords, private keys and passphrases are stored encrypted and are not returned to the browser after saving. Leaving an existing secret field blank preserves the saved value.
Use Own Infrastructure with a Content Brief
Pull source → Compare
Before editing, pull the current remote source into a reviewable Pending Change. Apply only the expected remote differences so Builder starts from the current release.
Prepare the Content Brief change
Open the AI Visibility Content Brief and work manually in Builder or approve Generate content draft.
Review and Apply
Inspect the exact project diff. Apply updates Builder source and records the task checkpoint but does not yet prove a public deployment.
Deploy to Own Infrastructure
Use the project's normal Deploy action with the saved target. Aetherion transfers source through SFTP, runs the restricted build, creates a recoverable backup and activates the public release.
Check deployment
After the production deployment is Ready, return to Action Center and verify the live route before starting a provider retest.
SSH/SFTP is not ordinary FTP
Own Infrastructure uses encrypted SSH/SFTP, verified host identity, separate source and public paths, backup-before-write and a recorded deployment workflow. Do not substitute an unrestricted FTP account.
Need project-specific help?
Open the private Help Center or create a support ticket with the affected project, route and request ID.