About Dropslate

Dropslate started as a local-first publishing layer: a folder of files on one machine, scheduled precisely, with nothing hidden about what would happen next. That idea - files stay yours, the schedule stays visible, a failure says why - carried over when it grew into a hosted product for teams who publish to more than one network.

We are a small team building the product we wanted to use ourselves: cheaper than the alternatives when an AI agent is part of the workflow, honest about the four things that can happen to a post, and priced so a solo creator can actually start on the free plan.

What we believe

• Precise. Every state, date, destination and action is explicit - never a vague "processing".
• Calm. The interface removes noise instead of adding animation for its own sake.
• Honest. Real status is shown; errors are the network’s own words, not ours softened.
• Local-first. Your files, uploaded once, are yours - not locked behind our export tool.
• Schedule-driven. The queue and the timeline are the core of the product, not an afterthought feature.

We write about how the product is built on the blog, and keep a plain changelog of what shipped and when.

Questions, feedback, or a bug to report: contact us.