As a relational database, Onspring lets you connect any of your data sets and records in logical relationships, from parent/child to sibling connections. Joining records provides very flexible reporting options, workflow automation and easily maintained access control.
A spoiled vacation resulted in the fortuitous availability of Onspring’s CTO, Chad Kreimendahl, when we experienced our first downtime in several years. Chad explains what happened, why it happened and how our technical team resolved the issue.
Have you created a software Frankenstein? Though the intent of your creation may have been something beautiful, the positive aspects of the design are quickly overshadowed by glaring design issues. This ultimately results in an army of villagers (your customers) chasing you down with fire and pitchforks. Chad Kreimendahl explains how to get yourself out of this monstrous dilemma.
We know from reporting on the Equifax data breach that names, social security numbers, email addresses, and physical addresses were taken. This confirmation of the email in the wild should be considered a terrifying confirmation that the rest is also out there, or may be soon.
I’ve been asked, on many occasions, how Onspring goes about being so insanely fast and responsive as a product. The most recent encounter related to a customer who has users spread all throughout the world. Their specific query was how their users in Asia were seeing absolutely no performance impact in the way one would expect when hitting our data center in the heart of the United States. Their average response time when making requests from their Asian offices to Onspring was less than 1/3rd of a second. That’s below 0.3 seconds per request. How is that possible?
If you’re an expert in your industry who’s designing a product or service, there’s a strong possibility that you’ve been a victim to this monster we call Design Hubris. Some of us are more susceptible than others, and the effects are almost always permanent, because they hit you early and they hit you deep. They spread like a virus, infecting all subsequent decisions and features.
At Onspring, we’ve spent much of our time and effort, both in product design and simply running our business, avoiding the “boogeymen” that disrupt so many forward-thinking companies. Running this gauntlet of ghouls has taught us many things, and the lessons of our former lives have frequently guided us when we might otherwise have wandered in the dark.
A quick Google search for “internal audit software” reveals a long list of available solutions. Many of these providers (Onspring included) exhibited at the recent Governance, Risk and Controls (GRC) Conference in Phoenix, co-sponsored by the IIA and ISACA. In terms of sheer quantity of choices, internal auditors have no shortage of software at their disposal. But how many of these solutions enable internal auditors to (as the IIA Research Foundation report describes) “creatively innovate to stay a step ahead of the real-time pace of technology advancement”?
In reality, cloud technologies for business allow you to get to the eventuality of “do a lot more with less.” And that often requires understanding that moving to any new technology will be an evolution more often than it’s a revolution. Included below are nearly all of the numerous reasons why you should consider cloud based business technologies, what we once called Software-as-a-Service or SaaS.
For the most part, technology has changed our lives for the better. Technology in business definitely makes our jobs easier, reduces costs and allows many of us to provide products and services we never thought possible. All that being said, it’s still fun to think about the past and reminisce about the “old days” in life and business. The way things have changed can almost always be traced back to some type of technology. I’m not talking about dinosaur days or the old west, but how quickly things have changed over the last 25 years or so.
When we founded Onspring back in 2010, we needed a great set of tools—including high-performance, easy-to-use databases and excellent development frameworks. In those days, some of the tools we needed didn’t exist or weren’t mature enough to be of any real value. We made do with what we could find at the time, always with an eye toward the future.