Stream Axis M3068-P 12MP 360° Panoramic Dome to Self-Hosted
Enterprise 360-degree panoramic camera with native FTPS and SFTP cloud streaming. Follow our step-by-step setup guide below to stream footage directly to Self-Hosted via FTP/S with Rilavek as the pipe — zero on-prem NVR required.
Your Axis M3068-P uploads footage offsite in real time directly to Self-Hosted. Intruders cannot steal or destroy evidence by seizing on-prem recorder hardware.
Store Axis M3068-P recordings in Self-Hosted on your own terms. Apply automated bucket lifecycle rules to roll over or archive clips after 30, 90, or 365 days.
Rilavek ingests native FTP/S streams from your Axis M3068-P and writes them directly to Self-Hosted via multipart S3 PUTs with zero disk writes.
How to Stream Axis M3068-P 12MP 360° Panoramic Dome to Self-Hosted
Follow these 6 steps to provision your object storage, configure Rilavek’s Data Store, Sender, and Ingestion Pipe, enter your camera firmware settings, and establish automated S3 retention rules.
Set Up Your 
Self-Hosted Bucket & Generate API Keys
Configure your target bucket and API credentials inside Self-Hosted so Rilavek can stream motion clips and continuous video directly into your storage.
- Access your RustFS Web Console or CLI and create your surveillance storage bucket.
- Under Access Keys, generate an Access Key and Secret Key pair with read/write policy.
- Ensure your RustFS instance is accessible via HTTPS (or Cloudflare Tunnel) on your configured port (e.g.
https://rustfs.local:9000).
Add Your Data Store in Rilavek
In your Rilavek dashboard, navigate to Data Stores > New Data Store, select your provider, and enter your S3 credentials. Rilavek verifies the connection with an automated write-probe before saving.
Add New Data Store
Create a Camera Sender in Rilavek
Go to Senders in the Rilavek sidebar and click New Sender. A Sender represents the hardware identity of your Axis M3068-P 12MP 360° Panoramic Dome and generates a dedicated device-level password.
Create New Sender
Must be at least 6 characters, lowercase, start with a letter/underscore, and contain only letters, numbers, hyphens, or underscores.
Secure credentials will be automatically generated for this sender.
Sender Credentials
Create & Configure Your Ingestion Pipe in Rilavek
Go to Pipes in the sidebar and click Create Pipe. Configure the 4 core sections of your pipeline: General (Pipe ID), Inputs (FTP), Access Control (Sender permission), and Destinations (Data Store).
1General Settings (Pipe ID)
Every pipeline in Rilavek is assigned an immutable, globally unique Pipe ID (e.g. p_cctv9x). This ID acts as an isolated ingestion channel that segregates audit logs, real-time transfer metrics, and storage routing. It also forms the second half of your scoped camera FTP login username (username@p_cctv9x).
Pipe ID
Use this ID to identify this pipe in logs. Combine it with the sender username for complete authentication details.
2Inputs (FTP / FTPS Ingress)
The Inputs configuration defines how camera files enter Rilavek. Enabling the FTP Ingress input provides a persistent, high-availability ingestion server (ftp.rilavek.com) compatible with active and passive FTP modes, explicit TLS negotiation, and standard CCTV firmware video push routines.
Inputs
Enable inputs to receive data.
FTP Ingress
Endpoint enabled. Connect using your Sender credentials.
Example: cam_m3068p@p_cctv9x
Use the password configured for the specific Sender.
3Access Control (Sender Authorization)
Access Control prevents unauthorized uploads by enforcing a zero-trust boundary on the ingestion pipe. Only explicitly authorized Senders (such as Axis M3068-P 12MP 360° Panoramic Dome) can authenticate and stream video into this pipe. Any requests with unassigned credentials are rejected at the network edge.
Access Control
Restricts who can upload to this pipe.
Individual Senders
Grant or revoke pipe access for specific individual senders.
4Destinations (Target Cloud Storage Routing)
The Destinations section routes video clips to your target cloud storage provider. Linking your configured Data Store routes all received footage directly to your Self-Hosted bucket (cctv-axis-recordings). Video files are committed on-the-fly via parallel multipart S3 PUTs without intermediate disk caching.
Destinations
This is where we send your files to.
Configure FTP, Motion Detection & Linkage Method in Axis M3068-P 12MP 360° Panoramic Dome Firmware
Open your camera's web configuration page in your browser at its local LAN IP address and complete the steps below:
Step 5AConfigure FTP Streaming Credentials
Click System > Events > Recipients (Add FTP / SFTP).
Navigate to Events > Recipients and click 'Add...' to open the Recipient Setup dialog. Name the recipient 'Recipient_FTP', set Type to 'FTP', enter your Rilavek Ingestion Host, port 21, scoped username, and device password. Ensure 'Use passive mode' is checked as indicated below.
Recipients
| Name | Type | Address | Upload path | User name |
|---|---|---|---|---|
| Recipient_FTP | FTP | ftp.rilavek.com | /axis-panoramic/ | cam_m3068p@p_cctv9x |
cam_m3068p@p_cctv9x (Sender@Pipe).Step 5BConfigure Action Rule Trigger (VMD 4 / Motion Analytics)
Click Events > Action Rules > Add.
Navigate to Events > Action Rules and click 'Add...'. Check 'Enable rule', name it 'FTP_Motion_Upload', and configure Condition > Trigger to 'Applications' with 'VMD 4: Any Profile' (Axis Video Motion Detection) so camera recording triggers on motion.
Action Rules
| Name | Trigger | Schedule | Action | Recipient |
|---|---|---|---|---|
| SFTP-Upload | Time - Recurrence | Continuous-Uploading | Send Video Clip | SFTP: ftp.cameraftp.com |
Step 5CLink Action Rule to FTP Recipient (Image & Video Upload)
Click Events > Action Rules > Actions.
Under Actions in the Action Rule Setup dialog, set Type to 'Send Images' (or 'Send Video Clip'), configure Stream profile and frequency, select 'Recipient_FTP' as Recipient, and check 'Add date/time suffix' for Base file name. Click OK to start streaming.
Axis Firmware Notes & Best Practices
Model-specific nuances, recommended settings, and verified workarounds for the M3068-P
Axis cameras use an Event / Recipient architecture. You create Rilavek as a 'Recipient', then attach an 'Action Rule'.
Verify Ingestion
Click Test in your camera's FTP settings or trigger a test recording transfer. In your Rilavek dashboard, navigate to Pipes > your pipeline > Transfers tab to inspect incoming files as video clips stream into Self-Hosted.
| FILE | SENDER | SIZE | DATE | STATE |
|---|---|---|---|---|
axis/m3068-p/2026-09-10/ch01_143000.mp4 | cam_m3068p | 18.4 MB | Sep 10, 14:30 | Success |
axis/m3068-p/2026-09-10/ch01_142500.mp4 | cam_m3068p | 21.2 MB | Sep 10, 14:25 | Success |
axis/m3068-p/2026-09-10/ch01_142000.mp4 | cam_m3068p | 19.7 MB | Sep 10, 14:20 | Success |
Common questions
Does the Axis M3068-P 12MP 360° Panoramic Dome require an on-site NVR to stream to Self-Hosted?
No. The Axis M3068-P 12MP 360° Panoramic Dome has built-in FTP client firmware. It connects directly to Rilavek's cloud bridge on port 21, streaming video chunks into your Self-Hosted bucket without requiring a local NVR or PC.
How does retention work on Self-Hosted?
You define exact retention policies (e.g. 30, 90, or 365 days) directly in your Self-Hosted bucket using standard S3 Lifecycle expiration rules. Footage is never auto-overwritten by proprietary cloud caps.
What happens if my internet connection drops?
If your M3068-P has a local MicroSD card installed, it records motion events locally and retries the FTP upload once connectivity is restored.
Stream Axis M3068-P 12MP 360° Panoramic Dome to Self-Hosted
Create your free Rilavek ingestion pipe in seconds. No NVR hardware, no proprietary camera cloud subscriptions, and 100% data ownership in your private storage bucket.
Free plan includes 10GB of transfer. No credit card required.