Deploy contentat scale. Knowexactly what posted.
Built for publishing across platforms. Designed for reliability, scale, and proof.
| Post | Media | Platforms | Lifecycle | Outcome | Published At | Scheduled For | Actions | ||
|---|---|---|---|---|---|---|---|---|---|
Release 2.4 — Improved retry classification
Delivery failures now grouped by terminal vs transient states. Cleaner observability. Fewer false degradation signals. |  | Scheduled | Pending | - | 2026-02-21 09:00 | ||||
Release 2.5 — Delivery queue optimization
Reduced scheduling latency under high concurrency. Improved throughput stability. |  | Attention | 1/4 failed | - | 2026-02-21 11:30 | ||||
Same content | | Signalbase HQ @signalbasehq | Published | Good | 2026-02-21 11:31 | 2026-02-21 11:30 | |||
Same content | | Signalbase @signalbase.io | Published | Good | 2026-02-21 11:31 | 2026-02-21 11:30 | |||
Release 2.5 — Delivery queue optimization. Reduced scheduling latency under high concurrency. | | Signalbase @signalbase | Error | Failing | - | 2026-02-21 11:30 | |||
Same content | | Signalbase @signalbase@mastodon.social | Published | Good | 2026-02-21 11:32 | 2026-02-21 11:30 | |||
Bulk import — XLSX and Markdown support
Structured ingestion for high-volume publishing workflows. |  | Completed | 4/4 | 2026-02-20 09:02 | 2026-02-20 09:00 | ||||
Asset library — Reference by ID
Upload once. Reuse across scheduled posts. |  | Completed | 4/4 | 2026-02-20 10:33 | 2026-02-20 10:30 | ||||
Scheduling — Deterministic scheduling
Consistent timestamp normalization across timezones. |  | Completed | 4/4 | 2026-02-20 12:03 | 2026-02-20 12:00 | ||||
Observability — Expanded delivery logs
Retry attempts and terminal states now fully traceable per platform. |  | Completed | 3/4 | 2026-02-20 13:46 | 2026-02-20 13:45 | ||||
Infrastructure — Improved timezone normalization
DST edge cases resolved across scheduled deliveries. |  | Completed | 4/4 | 2026-02-20 15:18 | 2026-02-20 15:15 |
Most tools help you create.Crossly makes sure it ships.
A publishing engine, not a content tool.
Lifecycle
Every post has an explicit state.
{
"event_type": "delivery.attempt_started",
"post_id": "pst_02a94",
"status": "running",
"attempt": 1,
"source": "delivery-engine",
"attempted_at": "2026-03-01T10:00:02Z",
"platform": "x",
"attempt_id": "att_8d11a"
}Failures are classified. Retries are logged. Permalinks are stored.
Nothing is assumed. Everything is recorded.
1.0 Schedule →
Schedule with precision.
Queue hundreds of posts across every channel. No wizard. No AI slop. Just your content, where you said it would be, when you said it would be there.
- 1.1 Bulk imports
- 1.2 Variant control
- 1.3 Timezone-aware routing
- 1.4 Impact preview before commit
2.0 Deliver →
Delivery is verified.
Every post. Every platform. Every status. You always know what went out and what did not, without checking twelve tabs.
- 2.1 Retry logic
- 2.2 Failure classification
- 2.3 Permalink logging
- 2.4 Explicit state transitions
3.0 Operate →
Operate at scale.
Built for operators managing dozens of accounts, not creators posting twice a week. Bulk ingestion, pipeline control, swimlane timelines per project.
- 3.1 Bulk ingestion
- 3.2 Pipeline control
- 3.3 Swimlane timelines
- 3.4 Multi-workspace control
4.0 Optional →
Post immediately.
Post on the go with the Crossly app.
5.0 Philosophy →
Designed for clarity.
No growth dashboards.
No engagement metrics.
No content suggestions.
Crossly does not influence what you say.
It ensures it gets delivered.
Available now.
Connect accounts. Ingest content. Publish with proof.